Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Orbit » org.aopalliance bundle do not specify version on exported packages
org.aopalliance bundle do not specify version on exported packages [message #564375] Wed, 10 September 2008 10:03
Frederic Conrotte is currently offline Frederic ConrotteFriend
Messages: 125
Registered: July 2009
Senior Member
Hello,

Following discussions about Xalan, Xerces libraries and Riena's problems
with package versioning, I have the same kind of problem in Eclipse OFMP
regarding the org.aopalliance bundle provided by Eclipse.

One of OFMP external dependencies requires
Import-Package: org.aopalliance.aop; version="1.0.0",
org.aopalliance.intercept; version="1.0.0"

But the org.aopalliance provided by Eclipse does not specify versions of
exported packages:
org.aopalliance/MANIFEST/MANIFEST.MF
(...)
Export-Package: org.aopalliance.aop, org.aopalliance.intercept
Bundle-Version: 1.0.0

instead of

Export-Package: org.aopalliance.aop; version="1.0.0",
org.aopalliance.intercept; version="1.0.0"

As reminder OSGi R4 specs specify that no version on exported or imported
packages defaults to 0.0.0 version instead of the "Bundle-Version" meta-tag
version

All these issues come from projects slowly moving to the OSGI best practice
of using "Import-Package" meta-tag instead of "Require-Bundle", which is a
good thing.
I agree with Jeff's point that it should be an Orbit-wide effort/policy to
specify imported/exported packages versions.

Should I file a bug for this to the Eclipse runtime project or should we
move org.aopalliance bundle to Orbit and fix it there ?

Thanks

Frederic
Previous Topic:Usage of the commons logging bundle.
Next Topic:org.aopalliance bundle do not specify version on exported packages
Goto Forum:
  


Current Time: Thu Nov 27 03:12:47 GMT 2014

Powered by FUDForum. Page generated in 0.02847 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software