-
-
Notifications
You must be signed in to change notification settings - Fork 300
Changes in 3.2.0
BJ Hargrave edited this page Mar 7, 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-Versionmanifest header, previous versions of this plugin always replaced the stringSNAPSHOTin the version qualifier with the value of the Bnd${tstamp}macro. The plugin now instead sets the Bnd instruction-snapshot: ${tstamp}. If the qualifier equalsSNAPSHOTor ends with-SNAPSHOT, the valueSNAPSHOTis replaced with the the value of the Bnd${tstamp}macro. Using the-snapshotinstruction allows the user to override the plugin behavior in thebnd.bndfile. For example, to retain the stringSNAPSHOTin the version qualifier, set-snapshot: SNAPSHOTin thebnd.bndfile. - 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 base directory of the project. - 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.
- TBD
-
ProjectBuilder, used for Workspace model builds, is changed to use the source output folder, e.g.binfolder, 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
SNAPSHOTis replaced with${tstamp}in theBundle-Versionheader 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.
- None at this time.
Dev Meetings Agenda/Protocol
Latest Releases
all versions
- 7.2.1 | 7.2.0
- 7.1.0 | 7.0.0
- 6.4.1 | 6.4.0 | 6.3.1 | 6.3.0
- 6.2.0 | 6.1.0 | 6.0.0
- 5.3.0 | 5.2.0 | 5.1.2 | 5.1.1
- 5.1.0 | 5.0.1 | 5.0.0
- 4.3.1 | 4.3.0 | 4.2.1 | 4.2.0
- 4.1.0 | 4.0.0
- 3.5.0 | 3.4.0 | 3.3.0 | 3.2.0
- 2.2.0
Gradle
- Plugin
- Build Customizations
- Builder & java-library
- Non-Workspace builds
- PluginManagement
- Using Kotlin
- Kotlin DSL jar config
- AntTasks
- Baselining [beta]
- Blurry Form Text on High-Resolution Displays
- Bnd toolchain parity table
- bnddistribute
- Buildpath Versions
- Conflict with M2E PDE Connector
- Eclipse Logging with Logback
- Hackathon June 2012
- Install bnd on the command line
- Is there a mailing list for bnd
- Launching Framework
- Multi-project build order
- Multi-release JAR support design discussion
- Plans wrt to enRoute
- Reading Eclipse project preferences in bnd
- Release Process
- Requirements for New Repository API
- Windows Locked Files
- WIP ideas ‐ bnd 8.0.0 breaking changes
- XML Attributes on Annotations
- [ant] Loading and Expanding Shared Headers or Properties