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

Bug 312250

Summary:	PDE Match Rules have no effect
Product:	z_Archived	Reporter:	Johannes Tysiak <mail>
Component:	Buckminster	Assignee:	buckminster.core-inbox <buckminster.core-inbox>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	P3	CC:	thomas
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Johannes Tysiak

2010-05-10 09:15:37 EDT

Build Identifier: Buckminster PDE Support - 1.2.0.r11404

In the BuckyBook section describing the eclipse.feature component type, the PDE Match Rules are explained. Using Buckminster PDE Support 1.2.0.r11404 in Helios M6, I have the following effect:

- Create a new Feature including plugin org.foo.bar in version 1.2.3
- Open the build.properties for the features and insert "pde.match.rule.default = perfect"
- View the generated CSPEC for the newly created feature

Expected outcome:
- The dependencies tab shows a dependency to org.foo.bar, version 1.2.3

Real outcome:
- The dependencies tab shows a dependency to org.foo.bar, version [1.2.0,1.3.0)


Reproducible: Always

Comment 1 Thomas Hallgren

2010-05-18 08:30:15 EDT

(In reply to comment #0)
> Expected outcome:
> - The dependencies tab shows a dependency to org.foo.bar, version 1.2.3
> 
The expected outcome for "perfect" is actually [1.2.3,1.2.3], i.e. exact match. If you just use 1.2.3 as a range, then it's interpreted as >= 1.2.3.

Changing the match rule will actually not affect the CSPEC immediately. This doesn't take effect until you execute the actual build and the only place where it becomes visible is in the p2 meta-data repository (the content.jar).