Bugzilla – Full Text Bug Listing
| Summary: | Cannot create 2 differents modeul with same name | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Francis ANDRE <francis.andre.kampbell> | ||||
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> | ||||
| Status: | CLOSED INVALID | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | igor, matthew | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
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". 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 @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. 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... |
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