Skip to content

Latest commit

 

History

History
117 lines (86 loc) · 3.83 KB

README.md

File metadata and controls

117 lines (86 loc) · 3.83 KB
Raw

Maven Plugins

The Bnd Maven Plugins require at least Maven 3.3.9.

This README, and the READMEs in the individual Bnd Maven Plugin folders, represent the capabilities and features of the Bnd Maven Plugins in the branch containing the READMEs. So for the master branch, this will be the latest development SNAPSHOT build. See the appropriate Git tag for the README for the Bnd Maven Plugin version you are using.

bnd-plugin-parent

This project builds the various Maven plugins provided by the Bnd project, and defines common dependency information.

These plugins are built using Maven (unlike the rest of Bnd) because it is very hard to build a Maven plugin unless you use Maven to do it!

bnd-maven-plugin

The core plugin, used to generate manifest and other metadata for projects that build an OSGi bundle.

bnd-indexer-maven-plugin

A plugin used to generate an OSGi repository index from a set of Maven dependencies. The entries in the index will reference the location of the bundles in the remote repositories to which they have been deployed.

bnd-baseline-maven-plugin

A plugin used to validate that a bundle correctly uses semantic versioning as described by the OSGi Alliance. This plugin will verify that the bundle and package versions of a module's output artifact are correct based on:

  • The bundle and package versions declared by the previously released version of the module.
  • Any changes that have been made to the packages exported by the bundle.
  • Any internal changes within the bundle.

bnd-export-maven-plugin

A plugin to export bndrun files.

bnd-resolver-maven-plugin

A plugin to resolve bndrun files.

bnd-testing-maven-plugin

A plugin to run integration tests from bndrun files.

bnd-run-maven-plugin

A plugin to run a bndrun file.

bnd-reporter-maven-plugin

A plugin to generate and export reports of projects.

Building the Maven Plugins

You must first run ./gradlew :build to build the Bnd artifacts and install them in your local maven repo. You can then run Maven to build the Bnd Maven plugins. You can run ./gradlew :maven:deploy to build the Bnd Maven plugins with the deploy goal which will deploy the built Bnd Maven plugins into the releaserepo.

Using the latest development SNAPSHOT build of the Bnd Maven Plugins

If you want to try the latest development SNAPSHOT build of the Bnd Maven Plugins, you will need to adjust your pom to refer to the snapshot repository and select the latest version of the plugins. For example, edit the pom's pluginManagement section, to configure the repository:

<pluginRepositories>
	<pluginRepository>
		<id>bnd-snapshots</id>
		<url>https://bndtools.jfrog.io/bndtools/libs-snapshot/</url>
		<layout>default</layout>
		<releases>
			<enabled>false</enabled>
		</releases>
	</pluginRepository>
</pluginRepositories>

Using the latest Milestone/Release Candidate build of the Bnd Maven Plugins

If you want to try the latest milestone or release candidate build of the Bnd Maven Plugins, you will need to adjust your pom to refer to the release repository and select the desired version of the plugins. For example, edit the pom's pluginManagement section, to configure the repository:

<pluginRepositories>
	<pluginRepository>
		<id>bnd-releases</id>
		<url>https://bndtools.jfrog.io/bndtools/libs-release/</url>
		<layout>default</layout>
		<snapshots>
			<enabled>false</enabled>
		</snapshots>
	</pluginRepository>
</pluginRepositories>