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

Bug 343900

Summary:	workspace feature ignored
Product:	[Eclipse Project] PDE	Reporter:	Jeff McAffer <jeffmcaffer>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:	stalebug

Description Jeff McAffer

2011-04-26 15:43:29 EDT

in M6...

I have a feature Foo in both the workspace and the target.  Foo is listed in a product configuration.  When running the product, the Foo feature from the target is used instead of the one from the workspace. This manifests itself in at least two ways:

- the one in the workspace lists more bundles and they are not present in the derived launch config
- double clicking on the feature in the product editor opens the feature from the target

Interestingly the one with the highest version is being selected.  Since the CVS form of most features have a version of X.Y.Z.qualifier and the built form is X.Y.Z.v20110404, and 'v' is greater than 'q', the one from the target is being used.  You can see this by changing the version of the one in the workspace and then revisiting the steps above.  With the higher version in the workspace, the workspace feature is used.

Note that this is all true when the product's feature entry is blank (or 0.0.0).  Not sure how long this behaviour has been in place but I'm just noticing now and suspect I would have noticed earlier in 3.7 as I did quite a bit of feature/product work...  In any event, it is pretty disconcerting and confusing.

Comment 1 Curtis Windatt

2011-04-27 15:18:32 EDT

Funny since there was a bug not too long ago complaining about PDE taking the workspace plug-in over the highest version.  Don't know when I'll have time to look at this, but obviously the behaviour should be consistent.

Comment 2 Eclipse Genie

2019-09-18 13:00:30 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.