Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Orbit » Orbit packages with versions]
Orbit packages with versions] [message #563854] Tue, 15 July 2008 12:42
Christian Campo is currently offline Christian CampoFriend
Messages: 597
Registered: July 2009
Senior Member
This is a multi-part message in MIME format.
--------------060001080305020201020704
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

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

--------------060001080305020201020704
Content-Type: message/rfc822;
name="Orbit packages with versions.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="Orbit packages with versions.eml"

Path: build.eclipse.org!not-for-mail
From: Christian Campo <christian.campo@compeople.de>
Newsgroups: eclipse.technology.equinox
Subject: Orbit packages with versions
Date: Fri, 11 Jul 2008 14:04:14 +0200
Organization: EclipseCorner
Message-ID: <g57i80$66g$1@build.eclipse.org>
NNTP-Posting-Host: frankfurt.compeople.eu
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: build.eclipse.org 1215777856 6352 80.153.43.238 (11 Jul 2008 12:04:16 GMT)
X-Complaints-To: news@build.eclipse.org
NNTP-Posting-Date: Fri, 11 Jul 2008 12:04:16 +0000 (UTC)
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
Xref: build.eclipse.org eclipse.technology.equinox:4905

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

--------------060001080305020201020704--
Previous Topic:org.apache.commons.logging: add buddy policy
Next Topic:org.apache.commons.logging: add buddy policy
Goto Forum:
  


Current Time: Thu Mar 28 14:23:22 GMT 2024

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

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

Back to the top