Eclipse Community Forums: Equinox » Orbit packages with versions

Home » Eclipse Projects » Equinox » Orbit packages with versions

Orbit packages with versions [message #113977]

Fri, 11 July 2008 08:04

Eclipse User

Hi,

Riena uses two components that are maintained in Orbit that we have slight problem with. One is org.apache.log4j and the
other is org.easymock. The problem is that the bundle specifies a bundle version but the packages have no such version.

Now we have a pretty keen user of Riena (a very nice person actually) who asked us the replace Require Bundle statements
in our manfest files with import package statements. We did that but found out that Equinox or the PDE is not able to
find a matching bundle if we import the package with version number.

The reason seems to be that if the bundle exports a package and does not specify a package version then it does not mean
(as I would assume) that the package version is the bundle version but it is no version. So asking for a specific
version of a package resolves to no bundle found.

1. Is that a bug or a feature that packages with no version info dont "inherit" the bundle version

2. I guess I have to bug the person who added the bundle to add the package version info ? right ?

thanks

christian campo

Re: Orbit packages with versions [message #115920 is a reply to message #113977]

Tue, 12 August 2008 10:37

Eclipse User

Originally posted by: eclipseng.arthorne.com

1. Feature.
2. Right.
--

Christian Campo wrote:
> Hi,
>
> Riena uses two components that are maintained in Orbit that we have
> slight problem with. One is org.apache.log4j and the other is
> org.easymock. The problem is that the bundle specifies a bundle version
> but the packages have no such version.
>
> Now we have a pretty keen user of Riena (a very nice person actually)
> who asked us the replace Require Bundle statements in our manfest files
> with import package statements. We did that but found out that Equinox
> or the PDE is not able to find a matching bundle if we import the
> package with version number.
>
> The reason seems to be that if the bundle exports a package and does not
> specify a package version then it does not mean (as I would assume) that
> the package version is the bundle version but it is no version. So
> asking for a specific version of a package resolves to no bundle found.
>
> 1. Is that a bug or a feature that packages with no version info dont
> "inherit" the bundle version
>
> 2. I guess I have to bug the person who added the bundle to add the
> package version info ? right ?
>
> thanks
>
> christian campo

Previous Topic:	How to "callback" to equinox platform from servlet?
Next Topic:	patch behavior

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 24 01:51:36 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter