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

On Tue, Jun 15, 2010 at 2:00 AM, Gunnar Wagenknecht
<gunnar@xxxxxxxxxxxxxxx> wrote:
> 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?

Won't this potentially cause problems out in the wild? is not a singleton, and if were to have both
versions of the plugin in your system a require bundle would pick up
the correct one ... an import package would always pick the version
exporting 2.0 packages (IIRC).  Perhaps not a bother since the
difference is the package versioning, but what about if the next
version of exports packages 1.3 ... as long as that
2.0 bundle version is in the system, it will be chosen over 1.3.

I thought this cause a problem when org.junit4 was exporting hamcrest
library packages at 4.5 (but really they were 1.0) and a consumer
wanted to use the hamcrest plugins which were exporting packages at
1.1.  We had to fix that before we shipped.

If I've misread what the problem was, I apologize for the question.


Paul Webster
Hi floor.  Make me a sammich! - GIR

Back to the top