Skip to content

Changes in 6.0.0

Jump to bottom Edit New page
Christoph edited this page Jul 7, 2021 · 37 revisions

Bnd/Bndtools 6.0.0

Bndtools

  • Bndtools is built to run on Eclipse 2020-06 (4.16) or later. This was changed from Eclipse 2018-12 (4.10) in the last release. So Bndtools 6.0 may not run on older versions of Eclipse.

Bndtools m2e

  • Bndtools m2e is built to run on Eclipse m2e 1.16.0 or later. This was changed from Eclipse m2e 1.10.0 in the last release. So Bndtools m2e 6.0 may not run on older versions of Eclipse m2e.

Bnd

  • Property naming prefix in cnf/ext/*.bnd changes - If an property name is already declared elsewhere, the file name will now be used as a namespace. In previous versions it has been used as a prefix. Before -plugin in cnf/ext/test.bnd became test.-plugin, now it will be -plugin.test.
  • A number of previously deprecated types and members have been removed. So code using these will need updates.

Bnd Command Line

  • TBD

Documentation

  • TBD

Bnd Maven Plugins

  • The Bnd Maven plugins now require a minimum of Maven 3.3.9. This was changed from Maven 3.1.1 in the last release.

Bnd Gradle Plugins

  • The Bnd Gradle plugins and tasks now support Gradle 7.
  • The Bnd Gradle plugins and tasks underwent a large update to modernize their implementations and prepare for Gradle 7 and newer Gradle idioms. All Bnd Gradle task properties are now Gradle Properties and should generally be set using an assignment in your build script. This also means the Gradle Properties are typed and expect the correct value when being set. So, using the Export task as an example, set the bndrun property with bndrun = file('mybndrun.bndrun') rather than bndrun 'mybndrun.bndrun'. With the change to use Gradle Properties, the latter example is no longer possible as Gradle expects the bndrun(String) method which does not exist. So you may need to update your build scripts to use assignment of the proper argument type for setting task properties.
  • Added outputBndrun property to the Resolve task type. This allows the resolve operation to write the resolution to an output bndrun file which can then be used as input to another task such as a TestOSGi task. Because the Bnd Gradle tasks use Gradle Properties, the connection of the outputBndrun output property of a Resolve task to the bndrun input property of a TestOSGi task, for example bndrun = resolveTask.flatMap { it.outputBndrun }, enables Gradle to know that the Resolve task must be executed before the TestOSGi task.
  • A number of previously deprecated task properties and task property setters/getters have been removed.
    • Baseline.destination is replaced by Baseline.reportFile.
    • Bndrun.workingDir is replaced by Bndrun.workingDirectory.
    • Export.destinationDir is replaced by Export.destinationDirectory.
    • Index.destinationDir is replaced by Index.destinationDirectory.
    • TestOSGi.resultsDir is replaced by TestOSGi.resultsDirectory.
  • Gradle is deprecating the convention concept and build scripts need to move to use the replacement extensions before Gradle 8.
    • BndPluginConvention is now deprecated and replaced by BndPluginExtension.
      • The bnd(), bndis(), bndMerge(), bndProcess(), and bndUnprocessed() methods in BndPluginConvention should no longer be used and build scripts should be updated to use the equivalent methods, get(), is(), merge(), process(), and unprocessed(), in the bnd extension. For example bnd.get('property') replaces bnd('property').
    • BundleTaskConvention is now deprecated and replaced by BundleTaskExtention.
      • The properties of the convention should no longer be used and build scripts should be updated to use the equivalent properties in the bundle extension. For example, bundle { bndfile = file('bnd.bnd') } replaces bndfile = file('bnd.bnd').
  • The Bnd Gradle plugins require a minimum of Gradle 6.7 for Java 8 to Java 15, and Gradle 7.0 for Java 16.

Backward compatibility

  • Bndtools is built to run on Eclipse 2020-06 (4.16) or later. So Bndtools 6.0 may not run on older versions of Eclipse.
  • Bndtools m2e is built to run on Eclipse m2e 1.16.0 or later. So Bndtools m2e 6.0 may not run on older versions of Eclipse m2e.
  • The Bnd Maven plugins require a minimum of Maven 3.3.9.
  • The Bnd Gradle plugins require a minimum of Gradle 6.7 for Java 8 to Java 15, and Gradle 7.0 for Java 16.
  • The Bnd Gradle plugins and tasks underwent a large update to modernize their implementations and prepare for Gradle 7 and newer Gradle idioms. All Bnd Gradle task properties are now Gradle Properties and should generally be set using an assignment in your build script. A number of previously deprecated task properties have been removed. The conventions are now deprecated and replaced by extensions. See above for more details.

Known Issues

Add a custom footer
Add a custom sidebar
Clone this wiki locally