• Intro Headers Instructions Macros Commands
  • Fork me on GitHub
    • Introduction
    • How to install bnd
    • Guided Tour
    • Guided Tour Workspace & Projects
    • Concepts
    • Best practices
    • Build
    • Project Setup
    • Generating JARs
    • Versioning
    • Baselining
    • Service Components
    • Metatype
    • Contracts
    • Bundle Annotations
    • Accessor Properties
    • SPI Annotations
    • Resolving Dependencies
    • Launching
    • Startlevels
    • Testing
    • Testing with Launchpad
    • Packaging Applications
    • JPMS Libraries
    • Wrapping Libraries to OSGi Bundles
    • Generating Documentation
    • Commands
    • For Developers
    • Tips for Windows users
    • Tools bound to bnd
    • Headers
    • Instruction Reference
    • Instruction Index
    • Macro Reference
    • Macro Index
    • Plugins
    • External Plugins
    • Settings
    • Errors
    • Warnings
    • Frequently Asked Questions
  • -resolve (manual|auto|beforelaunch|batch)

    The bnd workspace can use a resolver to calculate the content of the -runbundles instruction based on a set of initial requirements. The bndtools GUI can manually resolve the initial requirements but through the -resolve instruction it is possible to calculate the -runbundles when the file is saved or just before the -runbundles are used in the launch.

    The values are:

    • manual – It is up to the user to resolve the initial requirements
    • auto – Whenever the initial requirements are saved, the resolver will be used to set new -runbundles
    • beforelaunch – Calculate the -runbundles on demand. This ignores the value of the -runbundles and runs the resolver. The results of the resolver are cached. This cache works by creating a checksum over all the properties of the project.
    • batch – When running in batch mode, the run bundles will be resolved. In all other modes this will only resolve when the -runbundles are empty.

    Example

    -resolve beforelaunch
    
    • GitHub