Minor patch to the OSGi headers: add version ranges to imported packages

The attached patch makes the following adjustments to the OSGi headers:

1) imports are now versioned as "[v,v+1)" ie. treat all versions from the
current level, up to but not including the next major level, as compatible

2) re-enable calculation of "uses" clause, which helps with OSGi resolving

3) add dynamic import of AOP Alliance package, which lets developers start
using Guice without AOP but also means they can add the AOP bundle once
they want to intercept methods (previously we marked the AOP import as an
"optional" import, which means it's only checked for once when the bundle
resolves - whereas "dynamic" imports are checked whenever they're needed)

4) exclude some bogus imports that are discovered because we generate the
manifest based on the original classes that still have dependencies to the
pre-JarJar'd packages.

The last two changes are specific to the main Guice jar and therefore went
into "build.xml" rather than "common.xml". This patch also bumps the Bnd
Tool to the latest version, 0.0.305:

  http://www.aqute.biz/repo/biz/aQute/bnd/0.0.305/bnd-0.0.305.jar

This is a low priority issue because it merely improves the OSGi metadata
rather than fixes a bug, however it would be nice to see it added before
the next release :)

Original issue reported on code.google.com by mccu...@gmail.com on 10 Dec 2008 at 11:37

Attachments:

frjaeger220 / google-guice

Minor patch to the OSGi headers: add version ranges to imported packages #280