Changes in 3.2.0

Bnd 3.2.0

For Bndtools 3.2.0 changes, see https://github.com/bndtools/bndtools/wiki/Changes-in-3.2.0.

Bnd Maven Plugin Changes

bnd-maven-plugin

• When generating the Bundle-Version manifest header, previous versions of this plugin always replaced the string SNAPSHOT in the version qualifier with the value of the Bnd ${tstamp} macro. The plugin now instead sets the Bnd instruction -snapshot: ${tstamp}. This will replace the qualifier value of SNAPSHOT with the the value of the Bnd ${tstamp} macro. Using the -snapshot instruction allows the user to override the plugin behavior in the bnd.bnd file. For example, to retain the string SNAPSHOT as the version qualifier, set -snapshot: SNAPSHOT in the bnd.bnd file.
• The plugin will avoid building and writing output if none of the input files to the bundle are changed. This helps with incremental builds in M2E.

Bnd Gradle Plugin Changes

• TBD

Other Notable Changes

• ProjectBuilder, used for Workspace model builds, is changed to use the source output folder, e.g. bin folder, as the default contents of the bundle if the project does not specify any of the following instructions: Private-Package, Export-Package, Include-Resource, -includeresource, or -resourceonly. If the project specifies any of these instructions, then they will fully control the contents of the bundle. This change will make the default behavior more like maven or gradle builds where the source built in the project is included in the resulting bundle without having to specify that it should be included.

Backwards compatibility

• The bnd-maven-plugin changed how SNAPSHOT is replaced with ${tstamp} in the Bundle-Version header value. See above for details.
• The Bnd annotations will be deprecated in a future release of Bnd. Please make plans to migrate to the OSGi Release 6 specified annotations which now offer more features than the bnd annotations.

Known Issues

• None at this time.