Changes in 3.3.0

Bnd 3.3.0

For Bndtools 3.3.0 changes, see https://github.com/bndtools/bndtools/wiki/Changes-in-3.3.0.

OSGiRepository

A new repository plugin, aQute.bnd.repository.osgi.OSGiRepository has been added to replace FixedIndexRepo. It serves the same role as FixedIndexRepo but uses the new HttpClient support from Bnd 3.2. Please migrate your use of FixedIndexRepo to aQute.bnd.repository.osgi.OSGiRepository.

Other Notable Changes

• A download progress plugin has been added to log Download messages when downloading files from repositories.
• -testpath will now use Strategy.LOWEST which is what -buildpath uses to find the lowest version of a bundle to satisfy the dependency.
• Exception reporting was improved to provide more information when an exception occurs. The exception will be logged to SLF4J at the DEBUG level, the exception type will be added to the Processor in addition to the exception message and InvocationTargetExceptions will be unwrapped before being added to the Processor.

Backwards compatibility

• Bnd 4.0, planned for Spring 2017, will move to Java 8 as the base runtime.
• The Bnd DS, metatype and versioning annotations are deprecated and support for them will be removed in Bnd 4.0. Please make plans to migrate to the OSGi Release 6 specified annotations which now offer more features than the bnd annotations.
• The OSGiRepository replaces the aQute.bnd.deployer.repository.FixedIndexRepo repository plugin which will be deprecated in the future. Please migrate to the OSGiRepository repository plugin.
• The MavenBndRepository replaces the aQute.bnd.deployer.repository.aether.AetherRepository repository plugin which is now deprecated. Please migrate to the MavenBndRepository repository plugin.
• The biz.aQute.junit bundle has updated to use Java 6 as the compile target. It was Java 5 in the Bnd 3.2 release.

Known Issues

• None at this time.