[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] feature dependency properties

Hi Scott,

Happy new year.
Here is the code that convert the "match" term to version ranges.  I figured it would be than trying to use words to describe this :)

		if (match.equals("perfect")) //$NON-NLS-1$
			return new VersionRange(version, true, version, true);

		org.osgi.framework.Version osgiVersion = PublisherHelper.toOSGiVersion(version);
		if (match.equals("equivalent")) { //$NON-NLS-1$
			Version upper = Version.createOSGi(osgiVersion.getMajor(), osgiVersion.getMinor() + 1, 0);
			return new VersionRange(version, true, upper, false);
		if (match.equals("compatible")) { //$NON-NLS-1$
			Version upper = Version.createOSGi(osgiVersion.getMajor() + 1, 0, 0);
			return new VersionRange(version, true, upper, false);
		if (match.equals("greaterOrEqual")) //$NON-NLS-1$
			return new VersionRange(version, true, new VersionRange(null).getMaximum(), true);
		return null;


-----Original Message-----
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Scott Lewis
Sent: January-22-14 4:07 PM
To: P2 developer discussions
Subject: [p2-dev] feature dependency properties


When defining a feature, it's of course possible to give other required features (on Dependencies tab of PDE or requires element in 
feature.xml).   If one adds a dependency on a required feature it's also 
possible to specify Dependency Properties (Version to match and Match Rule).

Is there a specification and/or examples of the p2 install-time behavior...for distinct values of the Version to match and Match Rule 
dependency properties?   The Eclipse help for that page in PDE doesn't 
seem to have much, and I would like to understand what exactly the install-time implications of these feature-level dependencies are (e.g. 
for the various Match Rules).



p2-dev mailing list