• Intro Headers Instructions Macros Commands
Fork me on GitHub
    • Getting Started
      • How to install bnd
      • Guided Tour
      • Guided Tour Workspace & Projects
      • FAQ - Frequently Asked Questions
    • Concepts and Practices
      • Introduction
      • Concepts
      • Best practices
    • Build and Development
      • Project Setup
      • Generating JARs
      • Versioning
      • Baselining
      • Service Components
      • Metatype
      • Contracts
      • Bundle Annotations
      • Accessor Properties
      • SPI Annotations
    • Dependency and Launching
      • Resolving Dependencies
      • Launching
      • Startlevels
    • Testing
      • Testing
      • Testing with Launchpad
    • Packaging and Distribution
      • Packaging Applications
      • JPMS Libraries
      • Wrapping Libraries to OSGi Bundles
    • Documentation and Tools
      • Generating Documentation
      • Commands
      • For Developers
      • Templates for Workspaces
      • Tips for Windows users
      • Tools bound to bnd
    • Reference Material
      • Reference
      • Headers
      • Instruction Reference
      • Instruction Index
      • Macro Reference
      • Macro Index
      • Plugins
      • External Plugins
    • Configuration and Troubleshooting
      • Settings
      • Errors
      • Warnings
  • wrap [options] <[jar-file]> <[...]>

    Description

    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 .bnd command because that has greater control. Even better is to wrap in bndtools.

    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.

    Synopsis

    Options

    [ -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
    

    Examples

    ` bnd wrap -classpath osgi.jar *.jar`

Search
    • Home