Apache maven-bundle-plugin 2.2.0 released!

January 17, 2011 By Stuart McCulloch

Today I released version 2.2.0 of the maven-bundle-plugin from Apache Felix. This release may look like a minor update because it only contains two fixes, but one of them is very important. The workhorse behind the maven-bundle-plugin, Peter Kriens’ bnd tool, has been upgraded from 0.0.384 to 1.15.0. The new version is much smarter in deciding which packages to export and import, and supports easy creation of Web Archive Bundles (WABs) which can act both as bundles and standard WAR files. Add numerous other small improvements and fixes to the mix and this should result in a much better experience overall.

Special mention should be made of the efforts of Juven Xu and Peter Kriens who worked together to add Nexus OSS staging to Peter’s Ant build. Previously bnd artifacts were manually uploaded by occasional third-party requests to MAVENUPLOAD, often a very laborious process. Third-party uploads to Maven Central have since been streamlined and automated with Nexus, but OSS hosting is still preferred by project owners who want to stage and check artifacts as part of their regular build process.

On behalf of all the OSGi developers who use the maven-bundle-plugin I’d like to thank Juven and Peter for their work getting the latest versions of bnd onto Maven Central!

  • Vladimir

    Hi Stuart, thank you for you work!

    We have experienced a problem with new version 2.2.0 of maven-bundle-plugin: in “Export-Package:” list of manifest all packages are listed w/o version tag as it used to be.

    Is it a bug in plugin or we are missing something in our plugin configuration?


    • http://twitter.com/mcculls Stuart McCulloch

      There was a change to the “bundleall” and “manifest” goal where it used to default to the bundle version when versioning exports – whereas now it defaults to no version, which was felt to be a safer default (you can find the discussion about this in the dev list archives, search for bnd upgrade).

      If you want someone to investigate further then we’ll need a test project to determine whether it is due to this change in defaults or something else (attach it to a new issue on Felix’s JIRA)

  • http://twitter.com/dpishchukhin Dmytro Pishchukhin

    Hi Stuart,

    do you have any plans to make the plug-in threadSafe to support Maven 3 multithreading?


    • http://twitter.com/mcculls Stuart McCulloch

      No plans as yet – but you can suggest this as a feature at https://issues.apache.org/jira/browse/FELIX/component/12311143 – and of course any patches would be welcome!

    • http://twitter.com/mcculls Stuart McCulloch

      No plans at the moment, but feel free to suggest it as a feature on Felix’s JIRA

  • Koko


    It seems since I changed the version of this dependency I have this warning in the build logs:
    [WARNING] POM for ‘biz.aQute:bndlib:pom:1.15.0:runtime’ is invalid.

    • http://twitter.com/mcculls Stuart McCulloch

      You can safely ignore that warning – it only occurs with Maven 2.x and should be fixed in the next release of bnd.