Eclipse Community Forums: Orbit » org.aopalliance bundle do not specify version on exported packages

Help

Home

Home » Eclipse Projects » Orbit » org.aopalliance bundle do not specify version on exported packages

Show: Today's Messages :: Show Polls :: Message Navigator

org.aopalliance bundle do not specify version on exported packages [message #14247]

Wed, 10 September 2008 10:03

Frederic Conrotte

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

Report message to a moderator

Re: org.aopalliance bundle do not specify version on exported packages [message #14269 is a reply to message #14247]

Sun, 14 September 2008 00:45

Eclipse User

Originally posted by: david_williams.linux.vnet.ibm.com

Frederic Conrotte wrote:
> ...
>
> 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 ?
>
>
I'm not sure what the Eclipse runtime project bug would be. Is that
where the third party bundle is now?
If so, then yes.
And .. you might open a second one saying they should move it to Orbit
where most third party bundles go. :)

Report message to a moderator

Re: org.aopalliance bundle do not specify version on exported packages [message #564420 is a reply to message #14247]

Sun, 14 September 2008 00:45

David Williams

Messages: 176
Registered: July 2009

Senior Member

Frederic Conrotte wrote:
> ...
>
> 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 ?
>
>
I'm not sure what the Eclipse runtime project bug would be. Is that
where the third party bundle is now?
If so, then yes.
And .. you might open a second one saying they should move it to Orbit
where most third party bundles go. :)

Report message to a moderator

Previous Topic:	org.aopalliance bundle do not specify version on exported packages
Next Topic:	Can't org.jdom with Ganymede

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Sep 22 15:26:28 GMT 2017

.:: Contact :: Home ::.