Bug 398169 - Duplicate launch configuration displayed in the run configuration panel while there is really only one
Summary: Duplicate launch configuration displayed in the run configuration panel while...
Status: CLOSED DUPLICATE of bug 361401
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.3   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-15 05:44 EST by Francis ANDRE CLA
Modified: 2013-01-15 06:35 EST (History)
1 user (show)

See Also:

Attachments
Java run configuration panel with 4 TSAPEchoCLient (31.57 KB, image/gif)
2013-01-15 05:44 EST, Francis ANDRE CLA 		no flags Details
duplicate launch TSAPEchoClient on the Eclipse ressource explorer view (20.42 KB, image/gif)
2013-01-15 05:45 EST, Francis ANDRE CLA 		no flags Details
WXP Explorer view of the Z:\OSI\iso.itu\osi\als\demo\run directory (60.23 KB, image/gif)
2013-01-15 05:46 EST, Francis ANDRE 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 Francis ANDRE CLA 2013-01-15 05:44:13 EST 
Created attachment 225619 [details]
Java run configuration panel with 4 TSAPEchoCLient

Hi

Using a  multi modules maven style project structure, one gets multiple presentation/rendering of the same launch configuration while there is really only one. See the attached pictures showing 4 times the TSAPEchoClient.launch configuration while the wxp explorer view shows only one.

Rgds
Comment 1 Francis ANDRE CLA 2013-01-15 05:45:07 EST 
Created attachment 225620 [details]
duplicate launch TSAPEchoClient on the Eclipse ressource explorer view
Comment 2 Francis ANDRE CLA 2013-01-15 05:46:22 EST 
Created attachment 225621 [details]
WXP Explorer view of the Z:\OSI\iso.itu\osi\als\demo\run directory
Comment 3 Dani Megert CLA 2013-01-15 06:35:22 EST 

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