• 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
  • -dsannotations-options SELECTORS
    Builder

    Options for controlling DS annotation processing.

    The -dsannotations-options instruction configures how DS component annotations are processed and what metadata is generated.

    -dsannotations-options: version;minimum=1.2.0;maximum=1.3.0
    

    The example above, will restrict the use of OSGi DS annotations to minimum 1.2.0 and maximum 1.3.0 version. The version number denotes that the users are free to use any version equal to or higher than 1.2.0 but less than or equal to 1.3.0, provided that the users have the DS annotations included on the build path.

    The following options are supported:

    option  
    inherit use DS annotations found in the class hierarchy of the component class. WARNING: Annotations are not inherited from the component’s super classes by default. The problem is that super classes from imported packages may be different at runtime than they were at build time. So it is always best to declare your annotations on the actual component class.
    felixExtensions enable features proprietary to Apache Felix SCR
    extender add the osgi.extender=osgi.component requirement to the manifest
    nocapabilities do not add osgi.service capabilities to the manifest
    norequirements do not add osgi.service requirements to the manifest
    version set the minimum and/or maximum version of the osgi.extender=osgi.component requirement added to the manifest
Search
    • Home