• Intro Headers Instructions Macros Commands
  • Fork me on GitHub
    • 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
    • Plain JUnit Testing with OSGi (PRELIMENARY)
    • Testing
    • Packaging Applications
    • Wrapping Libraries to OSGi Bundles
    • Commands
    • For Developers
    • Tools bound to bnd
    • Headers
    • Instruction Reference
    • Instruction Index
    • Macro Reference
    • Macro Index
    • Plugins
    • Settings
    • Errors
    • Warnings
    • Frequently Asked Questions
  • -builderignore PATH-SPEC ( ',' PATH-SPEC ) *

    Specified paths must be relative to the project. Each path represents a directory in a project to be ignored by the builder when deciding if the bundles of the project need to be built. This is processed for workspace model builds by the Bndtools builder in Eclipse and the Bnd Gradle plugin.

    This can be useful when the workspace is configured to use different output folders for Bndtools in Eclipse and for Gradle. For example:

    bin: ${if;${driver;gradle};build/classes/java/main;bin}
    testbin: ${if;${driver;gradle};build/classes/java/test;bin_test}
    target-dir: ${if;${driver;gradle};build/libs;generated}
    

    When configuring the workspace to use different output folders for Bndtools in Eclipse and for Gradle, you should also use -builderignore to instruct the builder to ignore the other builder’s output folders.

    -builderignore: ${if;${driver;gradle};bin,bin_test,generated;build}
    
    • GitHub