Changes in 7.1.0
See the Release section of the README for where to find Bnd/Bndtools.
This is a breaking release because we moved the code base to Java 17.
- Bndtools now requires Eclipse 4.25 (2022-09) or later.
- added help buttons to various panels linking to the corresponding Website or manual page.
- updated (bndtools.workspace.min) to OSGi R8. The project templates in org.bndtools.templates.osgi now expect this Workspace template.
- new Wizard for creating a Java OSGi Service (api, impl, consumer) on the new Project Templates section on the bndtools website.
- new search filter for Requirements and Capabilities
- new filter to hide optional requirements
- new filter to detect (problematic) capabilities which are exported by multiple bundles but with different package content (split package problem)
- show number of current results (after filtering) for Requirements and Capabilities
- Copy to clipboard via
Ctrl / Cmd + Cfor Requirements and Capabilities which copies their tooltip contents. This helps during debugging and communicating with others about it. - updated website about Resolutions View
- Double Clicking on an entry of the ResolutionsView (Requirements and Capabilities) now opens the Advanced Search of Repository Browser in the "Other" tab and prefills the fields for namespace and filter.
Tip: Did you know you can drag&drop selected entries from Resolutions View e.g. Requirements to the Customize imports panel of the .bnd-editor? This can become quite handy when you want to declare some requirements of a bundle as resolution:=optional.
- You can click Resolve multiple times now to keep multiple resolution results open. Can be useful to compare different resolution attempts.
- improved handling of versions which are added a bundle is added to
-runrequiresor-runbundlesvia drag&drop or added in the dialog. - The debug output of Resolution Failure result panel was extended
- a shorter summary at the top trying to better explain what could not be resolved
- a section explaining when some bundles were blacklisted on the
-runblacklistand prevented resolution
- double clicking on a result entry of an Advanced search (e.g. filter by package name) now opens the jar-file of the bundle. this is now same behavior as double clicking on a bundle-version in the repository browser without advanced search filtering
- added Copy to Clipboard submenu for different kinds of information
- fixed bug in
Package browser / Right-click / Refactoring / Rename Packagewhich now works again - fixed bug in BndPomRepository which could not address an OSGi bundle by Maven GAV coodinates. This is now consistent with MavenBndRepository and fixes problems with
bnd.bndcontent like this, where a bundle is addressed by GAV instead of bsn:
-buildpath: \
commons-cli:commons-cli;version=1.2.0,\
-includeresource: \
@${repo;commons-cli:commons-cli;latest},\
- TBD
- TBD
- All Bnd artifacts are built to run on Java 17 or later.
- Bndtools is built to run on Eclipse 4.25 (2022-09) or later. So Bndtools may not run on older versions of Eclipse.
- Bndtools m2e is built to run on Eclipse m2e 2.0.5 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-generate-maven-plugin's poorly named goalbnd-generatehas been renamedgenerate - The Bnd Gradle plugins require a minimum of Gradle 7.3.
- The Bnd Gradle plugins and tasks underwent an update for 7.0. A number of previously deprecated conventions have been removed.
-
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.