• 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
  • -buildrepo repo ( ',' repo ) *

    After bnd has build a project it creates 0 or more JARs. If the -buildrepo is set, the JARs are put into the given repositories. The syntax is as follows:

     -buildrepo   ::= repo ( ',' repo )*
     repo			::= NAME ( ';' NAME ('=' VALUE)? )*
    

    The instruction provides a name of a repository, the repository must exist in the workspace. Any properties added to the name are provided as properties in the release context and thus given to the repository.

    This feature was inspired by the Maven Bnd Repository. In the Maven development process, projects are installed in the local repository (usually ~/.m2/repository) so they can be shared with other Maven projects. Setting the -buildrepo to a Maven repository will allow a bnd workspace to participate in this process on equal footing. Every time the project is build, all its JARs are installed in the associated Maven repository.

    For example:

    -plugin.maven  \
    	aQute.bnd.repository.maven.provider.MavenBndRepository; \
    	name=Local
    	
    -buildrepo: Local
    

    The install process is taking place in-line with the build process. It is therefore recommended to only use this for local (i.e. file system based) installs.

    • GitHub