repository·master·Indexed 20 days ago
https://github.com/bndtools/bndA comprehensive toolset for OSGi development featuring bndlib for bundle metadata and dependency management, a versatile command line tool for workspace management and JAR processing, and an Eclipse GUI. The toolset includes plugins like JavaGen for source generation, aQute Remote for remote debugging, and the JUnit Platform Tester for test discovery and execution.
The bnd-indexer-maven-plugin is a bnd-based Maven plugin used to create OSGi repository indexes of bundles. These indexes are suitable for use in OSGi resolution and provisioning systems.
The plugin provides two distinct modes of operation:
index goal: Creates an index from Maven project dependencies. It uses remote repository URLs to reference dependencies, making it ideal for hosting an OSGi repository system on a remote server. The output includes an XML file and a parallel gzipped version.local-index goal: Creates an index from a local folder containing bundles. It uses relative URIs to reference the bundles, which is useful for local testing or when bundling all files into a single release (e.g., using maven-assembly-plugin).The Bnd Maven Plugins suite provides specialized tools for integrating OSGi development into Maven-based projects. These plugins require at least Maven 3.3.9.
Key plugins include:
bndrun files.bndrun files.bndrun files.bndrun file.Bnd/Bndtools is a comprehensive toolset for OSGi development. It automates the creation of manifest headers by analyzing class code, verifies settings, manages project dependencies, and provides tools for diffing JARs.
The ecosystem consists of several key components:
The aQute Remote project provides remote debugging support for bnd projects. It allows you to debug bundles and bndrun files on a remote machine running an OSGi framework with an agent installed. The architecture is optimized for small remote machines.
To use it, you must include the biz.aQute.remote.launcher in your -runpath and provide a -runremote instruction in your bnd or bndrun file.
The bnd tool is a versatile command line interface for OSGi development and workspace management. It supports the full workspace model, allowing you to build, test, and manage projects without external build tools like Gradle or Ant.
Key capabilities include:
add, remove, clean, build, compile, run.diff, flatten, extract, source (merge sources), wrap, print.dependencies, graph, maven, repo.debug, exportreport, verify, test.baseline, bump.To see a list of all available actions, run the command without a name:
bndThe bnd-generate-maven-plugin is a Maven plugin used to execute bnd generators. It provides a mechanism to run either system commands or external generator plugins.
The plugin provides two goals:
generate: Runs generators using the standard -buildpath (all Maven dependencies for the module).generate-test: Similar to generate, but also resolves test dependencies and makes them available via -testbuildpath.You can configure the plugin using standard Maven <configuration> elements (steps) or via a bndfile using the standard bnd -generate instruction. When using Maven steps, the plugin translates them into a -generate.maven: instruction for bnd.
<plugin>
<groupId>biz.aQute.bnd</groupId>
<artifactId>bnd-generate-maven-plugin</artifactId>
<version>${bnd.version}</version>
<executions>
<execution>
<phase>generate-sources</phase>
<goals>
<goal>generate</goal>
</goals>
</execution>
</executions>
</plugin>bnd is an OSGi engine used for creating and working with OSGi bundles. It consists of two primary components:
META-INF/MANIFEST.MF). This is used by build tools like Maven, Gradle, and Ant.The org.bndtools.facade.ExtensionFacade acts as a bridge between the Eclipse extension registry and OSGi Declarative Services (DS) components.
In standard Eclipse development, extensions are often static and tied to the workbench lifecycle, meaning you cannot restart a plugin without restarting the entire Workbench. By using ExtensionFacade, you can decouple extension implementations from the registry. This allows you to develop Eclipse plugins where the implementation bundles can be dynamically restarted (live coding/testing) without affecting the running Eclipse instance.
A workspace is a directory that provides the structure and context for developing and building OSGi projects. It acts as a cohesive set of bundles that can import and export bundles through repositories.
To be recognized as a workspace, a directory must contain a cnf/ directory with the following structure:
cnf/bnd.bnd: Makes bndlib recognize the cnf directory as a project.cnf/build.bnd: Contains workspace-wide properties and instructions.cnf/ext/: A directory for plugin setup files.It is recommended to name your workspace using a shared prefix of the bundle symbolic names of its constituents (e.g., com.acme.prime) to improve cohesion and traceability.
bnd add workspace com.acme.prime
cd com.acme.prime
ls
# Displays 'cnf'An OSGi bundle is a JAR file that provides encapsulation by explicitly importing and exporting a set of packages.
Key characteristics:
In the OSGi model, a package acts as a specification (similar to a Java interface), while the bundle provides the implementation.
The patch release documentation (found in docs/patch-release-documentation.md) outlines the workflow for MICRO version increases. Key technical details include:
master branch is NOT updated during a patch release.About.java is updated with a patch version constant containing 3 components.