• 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
  • -classpath FILE (',' FILE) *

    The -classpath instruction adds class path entries to a bnd file’s processing. It contains direct references to JARs through file paths or URLs. Entries on the class path are made available as imports and can be used as private or exported packages.

    -classpath: jar/foo.jar, jar/bar.jar
    

    If you need to get all JARs in a directory you could use the ${lsa} macro:

    -classpath: ${lsa;jar/*}
    

    This instruction should only be used when bnd is used in stand alone mode. In project mode (when you have a workspace), the -buildpath defines the actual class path. However, even in project mode any -classpath entries are added to the actual class path.

    • GitHub