dcwrap
Use
Creates a development component (DC) that wraps build artifacts.
Syntax
Syntax |
dcwrap -dcname|-n DCName -dcvendor|-v DCVendor -compartment|-c compartmentName -buildvariant|-b buildVariant [-assembly|-as assemblyPart] [-compilation|-co compilationValue] |
Options |
|
-dcname|-n DCName |
Name of the DC to be created. |
-dcvendor|-v DCVendor |
Vendor of the DC to be created. |
-compartment|c compartmentName |
The name of the compartment in which the DC to be created resides. |
-buildvariant|b buildVariant |
Specifies for which build variant the build artifact is wrapped. |
-assembly|as assemblyPart |
Comma-separated list of name value pairs. The name denotes the public part for assembly and the value denotes the file that should be included into the public part.
assembly_pp1=c:\somejar1.jar,assembly_pp2=c:\somejar2.jar |
-compilation|co compilationValue |
Comma-separated list of name value pairs. The name denotes the public part for compilation and the value denotes the file that should be included into the public part.
|
Description |
The command allows you to wrap Java specific build artifacts into a DC so that they can be used as part of a DC build. A development configuration must be already imported or loaded.
The DC to be created that wraps the build artifacts must not exist in the development configuration before. |
Example
The command dcwrap is of use if you want to embed Java build artifacts that have been created “outside” into a DC build. Below you see how a DC named extdc is created. This DC provides as the build result for the compilation public part api in build variant default the Jar special.jar
dcwrap -n extdc -v mycompany.org -c external -co api=special.jar -b default
Note that in SAP NetWeaver Developer Studio it is possible to create DCs that wrap external build results. These DCs are of type External Library.