Re: [p2-dev] Generation of feature metadata

[Jens Reimann <jens.reimann@xxxxxxxxxxxxxxx>]

Hallo Ian,

thanks for the explanation. The match rule was unset. And I figured out now that, depending on the match rule, the version range is created differently. I found it a bit awkward that when I put in a version, but no match rule, I do get "0.0.0". I would have expected the version instead, with the meaning "greaterOrEqual".

So as I understood it, this is more or less for historic reasons? And one should better use the "includes" and "plugins" mechanism?

But when I look there, is seems to me, that during generation of the repository information, "0.0.0" is being replaced with the current feature version. Which would only work, if you actually have this feature available.

I am currently working a software artifact repository [1], mainly for OSGi and Maven Tycho, and am trying to figure out how to best extract metadata and automatically generate a feature for that purpose.

Again, thanks for the explanation.

Jens

[1] https://github.com/ctron/package-drone

On 11/28/2014 08:16 PM, Ian Bull wrote:

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

_______________________________________________
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

-- 
IBH SYSTEMS GmbH
D-85235 Pfaffenhofen an der Glonn
Läutenring 43
Geschäftsführer / CEO: Dr. Thomas Heitzig

Amtsgericht München
Handelsregister Nummer  HRB 197959
USt ID: DE267945175

Office Munich
D 80992 München
Agnes-Pockels-Bogen 1
T +49 89 18 9 17 49 0

The information transmitted is intended only for the person or entity
to which it is addressed and may contain confidential and/or pivileged
material. Any review, retransmission, dissemination or other use of,
or taking of any action in reliance upon, this information by persons
or entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer.