Bug 398523 - .launch configuration are duplicated in a multi module project
Summary: .launch configuration are duplicated in a multi module project
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 normal with 5 votes (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on: 245412
Blocks:
  Show dependency tree
 
Reported: 2013-01-18 12:18 EST by Adib Saikali CLA
Modified: 2021-04-19 13:21 EDT (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adib Saikali CLA 2013-01-18 12:18:12 EST
I am a using a multi module project with a hierarchical setup, and all my .launch files show up twice once from the parent project and once for each child project. 

Assume the following layout.


parent/
   moule1/
     foo.launch 
   module2/
     bar.launch 

Then the eclipse run configurations will have four run configuration 
   foo
   foo
   bar
   bar

I think m2e should tell eclipse not to scan for .launch files in the parent project.
Comment 1 Fred Bricon CLA 2013-01-18 12:21:27 EST
Try workspace > maven > Check "hide folders of physically nested modules"
delete the projects from the workspace (not physically)
import them back as maven projects
Comment 2 Igor Fedorenko CLA 2013-01-18 12:30:37 EST
Lack of proper support for physically nested projects is a long standing issues with Eclipse Platform/Resources (see bug 245412, which was created as a clone of much older bug 35973) and there is nothing we can do from m2e. I'll keep this bugzilla open for future reference, but no work is planned until the issue is resolved at platform level.
Comment 3 Adib Saikali CLA 2013-01-18 13:55:07 EST
(In reply to comment #1)
> Try workspace > maven > Check "hide folders of physically nested modules"
> delete the projects from the workspace (not physically)
> import them back as maven projects

This seems to be working for me, in eliminating the double .lanuch configurations.
Comment 4 Eclipse Genie CLA 2015-02-07 16:59:24 EST
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.
Comment 5 David Vree CLA 2016-05-19 10:41:59 EDT
This problem most certainly still exists and is quite annoying.  I have a Maven project with 8 submodules and therefore have 16 run configurations listed -- instead of just 8.
Comment 6 Pavel Bekkerman CLA 2016-09-07 03:37:12 EDT
Please, reopen it.
I'm having this trouble with:

Eclipse Java EE IDE for Web Developers.
Version: Neon Release (4.6.0)
Build id: 20160613-1800
Comment 7 Hector Palacios CLA 2017-10-20 13:02:13 EDT
I was getting this problem in Eclipse Mars, and now I also get it under Oxygen.

It's a multiproject gradle, using the Eclipse plugin.
I do gradle eclipse
and the import existing gradle projects.

Then all the launch files in the tree from the project get duplicated.
Comment 8 Sebastian Flügge CLA 2018-08-28 11:52:51 EDT
I can confirm this issue for importing a multiproject Gradle project. The Launch configurations get imported for parent and child projects, which is really annoying, because we get a launch configuration three times in the dropdown menu.

Please reopen.
Comment 9 Balz Guenat CLA 2019-06-27 04:59:51 EDT
I have created a new report for this bug under the Platform/IDE component: https://bugs.eclipse.org/bugs/show_bug.cgi?id=548702
Comment 10 Denis Roy CLA 2021-04-19 13:21:57 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/