Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318145 - Bogus errors about multiple versions of singleton
Summary: Bogus errors about multiple versions of singleton
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 with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-28 05:19 EDT by Tomasz Zarna CLA
Modified: 2019-09-04 19:11 EDT (History)
1 user (show)

See Also:

Attachments
Plug-ins validation dialog (19.12 KB, image/png)
2010-06-28 05:21 EDT, Tomasz Zarna CLA 		no flags Details
View All 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 Tomasz Zarna CLA 2010-06-28 05:19:56 EDT 
I20100608-0911

Steps:
1. Checkout org.eclipse.compare.examples.xml, org.eclipse.compare.examples and org.eclipse.team.examples.filesystem using R3_6 tag
2. Apply patch from bug 316050
3. Try to launch self hosted Eclipse
=> You will receive a message saying that all 3 plug-ins have duplicated singleton versions e.g. "2 versions of singleton 'org.eclipse.compare.examples.xml' exists"

If you reverse the patch and apply it again you will get similar messages but this time saying that you have 3 (sic!) conflicts for each plug-in.

Restarting Eclipse fixes the issue.
Comment 1 Tomasz Zarna CLA 2010-06-28 05:21:46 EDT 
Created attachment 172873 [details]
Plug-ins validation dialog
Comment 2 Eclipse Genie CLA 2019-09-04 19:11:14 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.