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
_______________________________________________
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