[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Generation of feature metadata

What is the 'match rule' set to?Â

Typically features are included in the 'included features' tab, not the dependencies tab. The dependencies tab is a relic of the old update manager, and while we've tried to properly publish all parts of the feature.xml to p2, I'm sure there are some corner cases.

Cheers,
Ian

On Fri, Nov 28, 2014 at 12:52 AM, Jens Reimann <jens.reimann@xxxxxxxxxxxxxxx> wrote:
Hi,

I just compared the output of P2 metadata for a feature.xml and a have
question, since I am not sure how things are, as they are ;-)

feature.xml
---------------
 Â<includes
    Âid="test.feature2"
    Âversion="0.0.0"/>

 Â<requires>
   <import plugin="org.apache.commons.io"/>
   <import feature="test.feature3" version="1.0.0.qualifier"/>
 Â</requires>
---------------

Creates the following metadata:

content.xml
---------------
    <required namespace='org.eclipse.equinox.p2.iu'
name='test.feature2.feature.group'
range='[1.0.0.201411280937,1.0.0.201411280937]'/>
    <required namespace='org.eclipse.equinox.p2.iu'
name='org.apache.commons.io' range='0.0.0'/>
    <required namespace='org.eclipse.equinox.p2.iu'
name='test.feature3.feature.group' range='0.0.0'/>
---------------

What I don't understand is the fact, that when a specific version is
present (import feature) it creates "range=0.0.0" where when I specify
"0.0.0" it creates a build specific ID as range.

Hopefully somebody can explain it to me, or direct to some wiki page
which explains it ;-)

Thanks in advance!

Jens
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/p2-dev



--
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource