Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359200 - Cannot create 2 differents modeul with same name
Summary: Cannot create 2 differents modeul with same name
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-28 05:43 EDT by Francis ANDRE CLA
Modified: 2021-04-19 13:23 EDT (History)
2 users (show)

See Also:

Attachments
A screen of the target module/submodules design (187.37 KB, image/jpeg)
2011-09-28 05:43 EDT, 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 2011-09-28 05:43:00 EDT 
Created attachment 204159 [details]
A screen of the target module/submodules design

Hi

I want to declare 2 Maven super module projectA and projectB as follow


projectA
    |
    -------subModuleA
    |          |
    |          ---------foo
    |                                             
    |
    -------submoduleB
               |
               ---------foo


and m2e declares an Eclipse project "foo" for the first maven submodule foo which precludes the capacity to declare the second maven submodule.

IMO, the name of the Eclipse project created by the wizard should be the full qualified artifact concatened path as in this exemple

projectA.submoduleA.foo

and

projectA.submoduleB.foo

Rgds
Comment 1 Matthew Piggott CLA 2011-09-28 09:35:14 EDT 
Multiple Eclipse workspace projects cannot have the same name.  That said most, if not all m2e wizards have an Advanced section which allows specifying a "Name template".
Comment 2 Francis ANDRE CLA 2011-09-29 01:21:48 EDT 
Hi

Multiple Eclipse workspace projects cannot have the same name. That's the point and the Name Template in the Advanced tab propose only those templates

[artifactId]
[artifactId]-TRUNK
[artifactId]-[version]
[groupId].[artifactId]
[groupId].[artifactId]-TRUNK
[groupId].[artifactId]-[version]

which do not solve the problem.

In my case, I need [groupdId].[artifactId].[artifactId] to be instantiated into

projectA.submoduleA.foo
projectA.submoduleB.foo


Rgds
Comment 3 Igor Fedorenko CLA 2011-09-29 07:31:15 EDT 
@Francis

maven requires (groupId,artifactId,version) tuple to be unique, so "[groupId].[artifactId]-[version]" is guaranteed to allow import of any multi-module project that builds on command line. even if there are projects with duplicate (groupId,artifactId,version), it is still possible to import all projects by using import wizard multiple times with different templates. 

If you feel strongly about using templates based on parent backtrace, please provide a quality patch and we'll consider it. Otherwise, m2e developers have no plans to work on this enhancement request.
Comment 4 Francis ANDRE CLA 2011-09-30 13:29:01 EDT 
OK Guys... my mistake... but Maven should be able to have also a full qualifier with multiples multimodules artifacts, something similar to nested directories... (nope I know)

Sorry for the noise...
Comment 5 Denis Roy CLA 2021-04-19 13:23:59 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/