Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Goolge Guice ( Bundle in Orbit exports wrong packages versions

We don't use package import but require bundle.
But we'll have a look.

Btw. As Sebastian already mentioned in the corresponding bugzilla, the bits from orbit are slightly modified, because Guice
generates new classes into existing packages. That causes problems if that package has been signed.


On Jun 15, 2010, at 8:31 AM, Ed Willink wrote:

Hi Gunnar

MDT/OCL inherits its dependency from Xtext where org.eclipse.xtext.util's MANIFEST.MF (1.19 in CVS as I write) has a minimum dependency of 2.0.0. It looks like Xtext needs to respin.


        Ed Willink

On 15/06/2010 07:00, Gunnar Wagenknecht wrote:
Greetings fellow Orbit committers and Cross-Project readers,

The Google Guice bundle in Orbit ( exports all of its
packages as version 2.0. However, this is incorrect and has been changed
to version 1.2 in Orbit CVS. The fix is committed but not released.

For details please have a look at:


If you import[.*] packages, please modify your bundles
to *not* import a specific version. This will ensure that your bundles
will not require any modification once the fixed bundle will be released.


Is there anything we can do to Helios to *not* have the wrong bundle go
out? I think it's too late. I also suspect that the number of consumers
is very low across the train (<=3). The fixed bundle still has a higher
bundle version. Therefore, p2 should upgrade systems fine. Thoughts?


No virus found in this incoming message. Checked by AVG - Version: 9.0.829 / Virus Database: 271.1.1/2937 - Release Date: 06/14/10 07:35:00

cross-project-issues-dev mailing list

Back to the top