Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312321 - Warn when > 1 instance of a singleton bundle is present in target/workspace
Summary: Warn when > 1 instance of a singleton bundle is present in target/workspace
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-10 14:51 EDT by Darin Wright CLA
Modified: 2019-09-09 02:30 EDT (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darin Wright CLA 2010-05-10 14:51:08 EDT 
Follow from bug 306684:

When the workspace or target platform contains more than one instance (different versions, or possibly the same version) of a single bundle present, an error or warning should be created. Generally, at launch time, it is bad to have more than one instance of a singleton.

The target state removes duplicates of the same version currently, but does not automatically remove duplicates when different versions of the same bundle are present (not sure how it would decide on which to remove).
Comment 1 Darin Wright CLA 2010-05-11 16:38:24 EDT 
Also investigate issues w.r.t products.
Comment 2 Curtis Windatt CLA 2010-07-27 15:08:54 EDT 
See also bug 290634.  The validation on launch configs checks for multiple copies of a singleton bundle.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:07:10 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.
Comment 4 Julian Honnen CLA 2019-09-09 02:30:00 EDT 
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.