Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 343038

Summary: Support "[name]" in in the "name template" (from <name/> in pom.xml) for importing projects
Product: z_Archived Reporter: Mark A. Ziesemer <bugs>
Component: m2eAssignee: Project Inbox <m2e.core-inbox>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3 CC: fbricon, igor
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Mark A. Ziesemer CLA 2011-04-16 10:30:22 EDT
While importing projects into Eclipse, the Maven Integration supports "name templates", e.g. "[groupId].[artifactId]-[version]", which simply refer to the elements of the same name in pom.xml.

Using "[name]" should do the same. However, it currently results in a project name of literally "[name]", without referring to the <name/> element in pom.xml.

Please correct me if I'm going down the wrong path here, but I treat "groupId" as a namespace, and "artifactId" as a "system name". Combining them with "version" results in a proper "finalName" for .jar file names, etc. (By default, the finalName is ${project.artifactId}-${project.version}.) "name" is more of a display name, and should be allowed to be used in the name templates if desired.

https://issues.sonatype.org/browse/MNGECLIPSE-897 would be an alternative option, using the name defined in Eclipse's .project file if it exists.

(This is a copy from https://issues.sonatype.org/browse/MNGECLIPSE-1216.  I was not the original reporter, who now only shows as "Deleted User".)
Comment 1 Igor Fedorenko CLA 2013-09-28 23:25:22 EDT
closing old/stale bugreport
Comment 2 Mark A. Ziesemer CLA 2013-09-28 23:49:35 EDT
This may be old, but I don't see anything to indicate that this is not still a valid issue.  Additionally, a retest just now on 1.4.0.20130601-0317 still shows this to be a current issue.  Please reconsider (or at least mark as "CLOSED WONTFIX", which might be a better indication here - if that is your true intent).
Comment 3 Igor Fedorenko CLA 2013-09-29 09:15:37 EDT
There was no activity on this bug for over two years, so I have to assume it is either invalid or simply is not important enough for anyone to do anything about it.
Comment 5 Mark A. Ziesemer CLA 2014-10-01 10:45:46 EDT
Thanks, Fred!!
Comment 6 Fred Bricon CLA 2014-11-12 10:28:23 EST
Maven 3.2.4 not released for Mars M3. Punting this issue to Mars M4
Comment 7 Denis Roy CLA 2021-04-19 13:23:42 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/