Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 321682

Summary: Relax feature version range policy to pde.match.rule.feature=compatible
Product: [RT] ECF Reporter: Markus Kuppe <bugs.eclipse.org>
Component: ecf.relengAssignee: Markus Kuppe <bugs.eclipse.org>
Status: RESOLVED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3 CC: slewis
Version: 3.3.0   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 327163    
Bug Blocks:    
Attachments:
Description Flags
differences in p2 metadata none

Description Markus Kuppe CLA 2010-08-04 04:26:05 EDT
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
Comment 1 Scott Lewis CLA 2010-08-09 13:59:23 EDT
+1 for changing version range policy for ECF features to 'compatible'.
Comment 2 Markus Kuppe CLA 2010-08-10 03:20:28 EDT
FWIW: ECF build has been changed to use "compatible" instead of "perfect" for now.
Comment 3 Markus Kuppe CLA 2010-08-10 03:31:27 EDT
A RT discussion has been started about this change [0].

[0] http://dev.eclipse.org/mhonarc/lists/rt-pmc/msg01973.html
Comment 4 Markus Kuppe CLA 2010-08-12 08:16:25 EDT
Created attachment 176459 [details]
differences in p2 metadata
Comment 5 Markus Kuppe CLA 2010-08-12 08:18:21 EDT
(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".
Comment 6 Scott Lewis CLA 2014-02-12 14:50:56 EST
This being done as part of refactoring effort in bug 409787

*** This bug has been marked as a duplicate of bug 409787 ***