• 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
  • -resolve.effective qname (',' qname )
    Workspace

    Set the use effectives for the resolver

    Each requirement and capability has an effective or is effective=resolve. An effective of resolve is always processed by the resolver.However, in (very) special cases it is necessary to provide more rules.

    The -resolve.effective syntax is as follows:

    -resolve.effective 	::= effective ( ',' effective )*
    effective		::= NAME (';skip:=' skip )
    skip			::= skip = '"' namespace ( ',' namespace ) * '"'
    

    The simplest model is to just list the names, for example:

    -resolve.effective: resolve,active
    

    In this case, the resolver will only look at requirements that are either resolve or active.

    Adding a meta effective could then be:

    -resolve.effective: resolve,active, meta
    

    However, in very, very rare (usually error) cases it is necessary to exclude certain namespaces. This can be done by using the skip: directive.

    -resolve.effective: resolve,active, meta;skip:='osgi.extender,osgi.wiring.package'
    
Search
    • Home