| org.aopalliance bundle do not specify version on exported packages [message #14247] |
Wed, 10 September 2008 06:03  |
Eclipse User |
|
|
|
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
|
|
|
| Re: org.aopalliance bundle do not specify version on exported packages [message #14269 is a reply to message #14247] |
Sat, 13 September 2008 20: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. :)
|
|
|
| Re: org.aopalliance bundle do not specify version on exported packages [message #564420 is a reply to message #14247] |
Sat, 13 September 2008 20:45 |
| Eclipse User |
|
|
|
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. :)
|
|
|
Powered by
FUDForum. Page generated in 0.03193 seconds
Home