-
-
Notifications
You must be signed in to change notification settings - Fork 302
Changes in 3.2.0
BJ Hargrave edited this page Mar 8, 2016
·
31 revisions
For Bndtools 3.2.0 changes, see https://github.com/bndtools/bndtools/wiki/Changes-in-3.2.0.
- When generating the
Bundle-Version
manifest header, previous versions of this plugin always replaced the stringSNAPSHOT
in the version qualifier with the value of the Bnd${tstamp}
macro. The plugin now instead sets the Bnd instruction-snapshot: ${tstamp}
. If the qualifier equalsSNAPSHOT
or ends with-SNAPSHOT
or.SNAPSHOT
, the valueSNAPSHOT
is replaced with the the value of the Bnd${tstamp}
macro. Using the-snapshot
instruction allows the user to override the plugin behavior in the project's bnd file. For example, to retain the stringSNAPSHOT
in the version qualifier, set-snapshot: SNAPSHOT
in the project's 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.
- A
<bndfile>
configuration element is defined to allow the specification of an alternate path for the project's bnd file. This path can be absolute or relative to the project's base directory. - A
<bnd>
configuration element is defined to allow the Bnd instructions to be specified in the pom file. This will generally be done via a<![CDATA[]]>
section in the<bnd>
element. The<bnd>
element will not be used if the project has a bnd file. - If
Bundle-SymbolicName
is not set in the project's bnd file, its value will default to the project's artifactId. - If
Bundle-Name
is not set in the project's bnd file, its value will default to the project's name.
- TBD
-
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.
- The bnd-maven-plugin changed how
SNAPSHOT
is replaced with${tstamp}
in theBundle-Version
header value. See above for details. - The bnd-maven-plugin changed the default value of the
Bundle-SymbolicName
header from the name of the project's base directory to the project's artifactId. - 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.
- None at this time.