importsca
Imports an Software Component Archive (SCA) into a development configuration. The command overrides the data in the target compartment. Therefore, we recommend you to save the content of the compartment first into which the SCA is imported. In this context, the preview option is useful to see which content the SCA has and what is going to be imported into the target compartment. What is really imported depends first on which archive types (source archives, build archives, deploy archives) the SAC contains, and which state the target compartment has. If the target compartment has source state, then only source archives are considered for import. If the target compartment has archive state then build archives and deploy archives are considered.
The specification of the target compartment is optional. If it is not specified it will be deduced from the SC name and SC vendor information the SCA metadata. In any case, the target compartment must match this data.
Syntax |
importsca -file|-f fileName [-mirror|-m] [-buildvariant|-b buildVariant] [-preview|-p] [-compartment|-c compartmentName] |
Options |
|
-file|-f fileName |
SCA file to be imported. |
[-mirror|-m] |
If enabled, the target compartment will contain exactly the same development components (DCs) as in the imported SCA. As a consequence, those DCs in the compartment that do not appear in the SCA will be deleted. |
[-buildvariant|-b buildVariant] |
The build variant is relevant for build and deploy archives. If no build variant is specified, an import is triggered for all build variants defined in the compartment. |
[-preview|-p] |
If enabled, the DCs are shown that will be imported into the target compartment. The import itself will not take place. |
[-compartment|-c compartmentName] |
The compartment into which the SCA shall be imported. If not specified the compartment is deduced from the metadata of the SCA. |
Description |
A development configuration must be already imported or loaded. The compartment specified in the SCA metadata must exist in the targetdevelopment configuration. |
importsca -f MyComponentrs.sca -b default –p
importsca -f MyComponentrs.sca -b default -mirror