[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] Fragment oddities
>From what I understand (this was explained to me a while back), fragments in the sense of OSGi and Fragments in the sense of p2 are two completely different things. The p2 metadata doesn't represent OSGi fragments as InstallableUnitFragments, these are represented as normal InstallableUnits.
IUFragments are used to declare fragments on the IU (translation properties on the IU for example).
I'm not sure if that made sense. ;)
On Wed, Sep 23, 2009 at 3:10 PM, Thomas Hallgren <thomas@xxxxxxx>
I'm looking at an IU that I was fairly sure was a fragment. The IU in question is the 'org.eclipse.swt.win32.win32.x86'.
When I read this IU using a query, it doesn't arrive as a IInstallableUnitFragment and when I look at it's XML in the content.jar, it doesn't have any hostRequirements. It's also missing the fragment signum:
<property name='org.eclipse.equinox.p2.type.fragment' value='true'/>
So I guess this isn't a fragment then, at least not from a P2 perspective? OSGi will see it as a fragment. The manifest contains:
and this entry can also be found. Not sure what it means, but perhaps it's some ancient way of declaring the host requirement?
<provided namespace='osgi.fragment' name='org.eclipse.swt' version='3.5.0.v3550b'/>
Can someone please explain why the IU is declared this way?
p2-dev mailing list
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource