Changes in 6.4.0
Clone this wiki locally
See the Release section of the README for where to find Bnd/Bndtools.
- Avoids JVM crash on macOS for an SWT bug when using Bndtools Explorer view.
- Support for Apple M1 bndrun file in development
- Fixed most issues in supporting the latest m2e (2.x).
- Added a cache option to the
-resolveinstruction. This will resolve on demand and use a cache when the workspace & project files are unchanged.
- Bugs fixed in jar signing support.
- Detects recursive macro expansion in properties when processing pom files.
- Added file resource cache to avoid multiple computations of a file's capabilities and requirements (including SHA-256 hash).
osfilemacro fixed to use OS specific separators.
- Baselining now avoids warnings at major version boundaries about missing baseline.
- Detects loops in
- Resolving adds a default native capability when not set.
- Now clears
- Versioning support for external plugins
- Improved loop detection in include files
- The old and out-of-date
enroutecommand has been removed.
- Updated to remove stale references to old enRoute material.
- Maven plugins all now support the
outputBndrunDirconfiguration parameter for
bnd-resolver-maven-pluginso you can specify the output directory to write the output bndrun files.
bndrunDirconfiguration parameter for
bnd-testing-maven-pluginso they can use the output bndrun files from a
bnd-resolver-maven-pluginexecution. For completeness, we also add the
bndrunDirconfiguration parameter to
- Use of Providers is supported for manifest attribute values.
- The default values for Bundle-SymbolicName and Bundle-Version are now task inputs.
- Bndtools is built to run on Eclipse 2020-06 (4.16) or later. So Bndtools 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 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, Gradle 7.0 for Java 16, and Gradle 7.3 for Java 17.
- The Bnd Gradle plugins and tasks underwent a large update in 6.0 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.
Eclipse m2e has a bug which can result in build looping. If you experience this, update Eclipse m2e to 1.18.2 or later which seems to have fixed the issue.
Windows 10 users: Windows 10 Defender significantly slows down Eclipse, reason being Windows 10 Defender scanning the JAR files. The problem has been reported to Microsoft here. Until then, a workaround to this problem is to add Eclipse root directory to Windows 10 Defender’s exclusion list, detailed steps are shared here.
Note: This is not just an Eclipse issue on Windows 10.
See also Bnd Tips for Windows users.