Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » p2.site of a feature contains wrong plugin versions
p2.site of a feature contains wrong plugin versions [message #545590] Thu, 08 July 2010 06:25 Go to next message
Mario Winterer is currently offline Mario Winterer
Messages: 136
Registered: July 2009
Senior Member
Hi!

I've some problems concerning plugin-versions when invoking "p2.site" on
a feature.
It seems that buckminster packs the newest plugin always even if the
feature.xml explicitely denotes a lower plugin version.

Example:
Feature org.eclipse.help (version 1.1.1.R35x_v20090811) lists the plugin
org.apache.commons.logging with version 1.0.4.v200904062259.

My target platform contains this plugin twice - once with this version
and once with version 1.1.1.v200904062255.

When I now invoke "p2.site" on this feature, the resulting p2 repository
contains only the newest version of org.apache.commons.logging.

As a result, installing this feature via director fails.

Can somebody please verify if this is a bug so that I can file it in
bugzilla?

(I'm using org.eclipse.buckminster.core.feature, version 1.3.0.r11467)

Thanks,
Mario
Re: p2.site of a feature contains wrong plugin versions [message #545592 is a reply to message #545590] Thu, 08 July 2010 06:53 Go to previous messageGo to next message
Erdal Karaca is currently offline Erdal Karaca
Messages: 701
Registered: July 2009
Senior Member
I have the same problem.
In my case commons.logging is even present in 3 different jars (2x1.0.4 and 1.1.1)...
If I use buckminster 3.5 there will be no problem...
Re: p2.site of a feature contains wrong plugin versions [message #545614 is a reply to message #545592] Thu, 08 July 2010 08:33 Go to previous messageGo to next message
Mario Winterer is currently offline Mario Winterer
Messages: 136
Registered: July 2009
Senior Member
Am 08.07.2010 12:53, schrieb Erdal Karaca:
> I have the same problem.
> In my case commons.logging is even present in 3 different jars (2x1.0.4
> and 1.1.1)...
> If I use buckminster 3.5 there will be no problem...

I've found out that it also works with buckminster 3.6 headless.
I've got the following warning when materializing into my workspace via
component query, but apart from that it works without errors:

WARNING [0000] : Component request
org.apache.commons.logging:osgi.bundle/[1.1.0,1.2.0) is inconflict with
request org.apache.commons.logging:osgi.bundle/[1.0.0,1.1.0)
Re: p2.site of a feature contains wrong plugin versions [message #545615 is a reply to message #545614] Thu, 08 July 2010 08:35 Go to previous messageGo to next message
Mario Winterer is currently offline Mario Winterer
Messages: 136
Registered: July 2009
Senior Member
Am 08.07.2010 14:33, schrieb Mario Winterer:
> Am 08.07.2010 12:53, schrieb Erdal Karaca:
>> I have the same problem.
>> In my case commons.logging is even present in 3 different jars (2x1.0.4
>> and 1.1.1)...
>> If I use buckminster 3.5 there will be no problem...
>
> I've found out that it also works with buckminster 3.6 headless.
> I've got the following warning when materializing into my workspace via
> component query, but apart from that it works without errors:
>
> WARNING [0000] : Component request
> org.apache.commons.logging:osgi.bundle/[1.1.0,1.2.0) is inconflict with
> request org.apache.commons.logging:osgi.bundle/[1.0.0,1.1.0)

Additional info: It works with headless buckminster 3.6 M6; I've not
tried the final release!
Re: p2.site of a feature contains wrong plugin versions [message #545772 is a reply to message #545590] Thu, 08 July 2010 23:32 Go to previous messageGo to next message
Miles Parker is currently offline Miles Parker
Messages: 1338
Registered: July 2009
Senior Member
I wonder if this has something to do wiht the org.junit issue..
Re: p2.site of a feature contains wrong plugin versions [message #545929 is a reply to message #545590] Fri, 09 July 2010 11:46 Go to previous message
Jason Barkanic is currently offline Jason Barkanic
Messages: 16
Registered: November 2009
Junior Member
I have similar problems that I think stem from the same root cause. I have features explicitly requesting particular versions of a bundle, but only the newest gets included in a repo built with site.p2.

Invoking a regular old feature export from the tooling works.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=319329
Previous Topic:No component named org.eclipse.equinox.launcher.motif.hpux.PA_RISC
Next Topic:How to deal with source features in rmap
Goto Forum:
  


Current Time: Thu Apr 17 05:53:10 EDT 2014

Powered by FUDForum. Page generated in 0.16485 seconds