Wrap a jar into a bundle. This is a poor man’s facility to quickly turn a non-OSGi JAR into an OSGi bundle. It is usually better to write a bnd file and use the bnd
The wrap command takes an existing JAR file and guesses the manifest headers that will make this JAR useful for an OSGi Service Platform. If the output file is not overridden, the name of the input file is used with a .bar extension. The default bnd file for the header calculation is:
Export-Package: * Import-Package: <packages inside the target jar>
If the target bundle has a manifest, the headers are merged with the properties.
The defaults can be overridden with a specific properties file.
[ -b, --bsn <string> ] - Set the bundle symbolic name to use [ -c, --classpath <string>* ] - A classpath specification [ -f, --force ] - Allow override of an existing file [ -i, -ignoremanifest ] - Do not include the manifest headers from the target bundle [ -o, --output <string> ] - Path to the output, default the name of the input jar with the '.bar' extension. If this is a directory, the output is place there. [ -p, --properties <string> ] - A file with properties in bnd format. [ -v, --version <version> ] - Set the version to use
` bnd wrap -classpath osgi.jar *.jar`