|Feature dependency match rules [message #39746]
||Fri, 09 January 2009 18:30
Originally posted by: eclipse-news.rizzoweb.com|
Is there any documentation that explains the precise meaning of each of
the Match Rule options for declaring a dependency version in feature.xml?
If not, can somone offer an explanation here? A wiki page would be
ideal, but I'll volunteer to create one if someone will give me the
|Re: Feature dependency match rules [message #39938 is a reply to message #39746]
||Mon, 12 January 2009 14:06
| Benjamin Cabé
Registered: July 2009
Location: Toulouse, France
In the feature manifest help
( http://help.eclipse.org/stable/topic/org.eclipse.platform.do c.isv/reference/misc/feature_manifest.html),
you'll find the following explanation:
*match* - optional matching rule. Valid values and processing are as
* if *version* attribute is not specifies, the match attribute (if
specified) is ignored.
* *perfect* - dependent plug-in version must match exactly the specified
version. If "patch" is "true", "perfect" is assumed and other values
cannot be set.
* *equivalent* - dependent plug-in version must be at least at the
version specified, or at a higher service level (major and minor version
levels must equal the specified version).
* *compatible* - dependent plug-in version must be at least at the
version specified, or at a higher service level or minor level (major
version level must equal the specified version).
* *greaterOrEqual* - dependent plug-in version must be at least at the
version specified, or at a higher service, minor or major level.
I think that would be reasonable to at least provide a link to the
previously mentioned page in the Feature Manifest Editor help page
( http://help.eclipse.org/stable/topic/org.eclipse.pde.doc.use r/guide/tools/editors/feature_editor/dependencies.htm)
My blog: http://blog.benjamin-cabe.com
Powered by FUDForum
. Page generated in 0.01588 seconds