Migration Guide

There are some breaking changes in BndTools 2 that require attention when migration from a previous version.

Repositories

A lot has changed in the repositories area. The most easy way to migrate is to rename your cnf project to something else, and let BndTools generate a new one. Dependencies from the old local repo should be added to the localrepo. You can do this by dragging the jar files from disk to the localrepo icon in the repository view.

The runrequire(s) syntax has changed.

Before:

-runrequire: bundle:(symbolicname=org.apache.felix.configadmin)

Now:

-runrequires: osgi.identity;filter:='(osgi.identity=org.apache.felix.scr)'

You can also use any other capability for the filter, e.g.:

-runrequires: osgi.extender;filter:='(&(osgi.extender=osgi.blueprint)(version>=1.0)(!(version>=2.0)))'

(see https://github.com/bndtools/bndtools/issues/512)

OSGi Framework version has changed

If you use the resolver in you bnd files you need to update the OSGi Framework version, the resolver will refuse to work otherwise.

The OSGi compendium bundle was moved

If projects rely (e.g. in the build path) on the osgi.cmpn bundle they need to be updated. Simply remove the osgi.cmpn bundle and re-add it.