[MECLIPSE-586] Using -Declipse.projectNameTemplate is broken on multi module projects

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.6, 2.7
• Component/s: Core : .project, Core : Dependencies resolution and build path (.classpath), Core : Multi-projects
• Environment: Maven version: 2.0.9; Java version: 1.6.0_10-rc; OS name: "linux" version: "2.6.27-14-generic" arch: "amd64" Family: "unix"
• Assignee: Robert Scholte
• Reporter: Baard Johansen
• Created: 09/Jul/09 10:22
• Updated: 25/Dec/15 11:49
• Resolved: 25/Dec/15 11:49

Description

In version 2.5.1 when specifying projectNameTemplate on the commandline, the .project file and references are generated correcly. In 2.6 and 2.7 the project has the correct name, but referenced projects is not using the specified pattern. This renderes the .project-file and .classpath useless.

Example (using mvn eclipse:eclipse Declipse.projectNameTemplate=trunk[artifactId]) where moduleA depends on moduleB:

moduleA/.project
<projectDescription>
<name>trunk-moduleA</name>
<projects>
<project>moduleB</project>
</projects>
[..]
</projectDescription>

moduleA/.classpath
<classpath>
[..]
<classpathentry kind="src" path="/moduleB"/>
</classpath>

moduleB/.project
<projectDescription>
<name>trunk-moduleB</name>
[..]
</projectDescription>

Issue Links

• is duplicated by: MECLIPSE-609 [regression] projectNameTemplate is not used in moltimodule <projects> in .project