Community
Participate
Working Groups
The currently implemented version range policy in ECF is quite strict ("perfect") [0]. To allow for easier consumption, it should be changed to "compatible" instead. The whole issue of feature version ranges is rather controversial [1] though and thus we might want to raise a discussion (on the rt-pmc ml) first?! [0] https://bugs.eclipse.org/309147 [1] http://dev.eclipse.org/mhonarc/lists/pde-dev/msg01799.html
+1 for changing version range policy for ECF features to 'compatible'.
FWIW: ECF build has been changed to use "compatible" instead of "perfect" for now.
A RT discussion has been started about this change [0]. [0] http://dev.eclipse.org/mhonarc/lists/rt-pmc/msg01973.html
Created attachment 176459 [details] differences in p2 metadata
(In reply to comment #4) > Created an attachment (id=176459) [details] > differences in p2 metadata This attachment contains two different versions of the SLP feature p2 metadata (just diff/compare to see the changes). slp-old.xml has been generated with "perfect", slp-new.xml with "compatible".
This being done as part of refactoring effort in bug 409787 *** This bug has been marked as a duplicate of bug 409787 ***