[
http://jira.codehaus.org/browse/MECLIPSE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183081#action_183081
]
Baard Johansen commented on MECLIPSE-586:
-----------------------------------------
Oops, the classpathentry in moduleA/.classpath was wrong. Should have been
"/moduleB".
> Using -Declipse.projectNameTemplate is broken on multi module projects
> ----------------------------------------------------------------------
>
> Key: MECLIPSE-586
> URL: http://jira.codehaus.org/browse/MECLIPSE-586
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : .project, Core : Dependencies resolution and
> build path (.classpath), Core : Multi-projects
> Affects Versions: 2.6, 2.7
> 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"
> Reporter: Baard Johansen
>
> 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="/moduleA"/>
> </classpath>
> moduleB/.project
> <projectDescription>
> <name>trunk-moduleB</name>
> [..]
> </projectDescription>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
