• Intro Headers Instructions Macros
  • Fork me on GitHub
    • Release
    • Introduction
    • How to install bnd
    • Guided Tour
    • Guided Tour Workspace & Projects
    • Concepts
    • Best practices
    • Build
    • Generating JARs
    • Versioning
    • Baselining
    • Service Components
    • Metatype
    • Contracts
    • Manifest Annotations
    • Resolving Dependencies
    • Launching
    • Testing
    • Packaging Applications
    • Wrapping Libraries to OSGi Bundles
    • From the command line
    • For Developers
    • Plugins
    • Tools bound to bnd
    • File Format
    • Header Reference
    • Instruction
    • Instruction Index
    • Macro Reference
    • Command Reference
    • Plugins Reference
    • Settings
    • Errors
    • Warnings
    • Frequently Asked Questions
    Supported by OSGi enRoute
  • package [options] <> <[...]>

    OPTIONS

    [ -j, –jpm ] - Use JPM to deliver the -runbundles and -runpath. This will include the SHAs of the jars in the manifest. When JPM installs such a JAR it will automatically fetchs these jars and place them in the proper place. The filepaths to these artifacts will contain a {JPMREPO} macro that points at the directory where the sha based named files are stored. [ -o, –output ] - Where to store the resulting file. Default the name of the bnd file with a .jar extension. [ -p, --profile ] - Profile name. Default no profile

    • Contact
    • Developers
    • More