You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@codehaus.org> on 2011/07/27 23:33:43 UTC
[jira] Updated: (MECLIPSE-586) Using -Declipse.projectNameTemplate
is broken on multi module projects
[ https://jira.codehaus.org/browse/MECLIPSE-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MECLIPSE-586:
------------------------------------
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>
was:
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>
Adjusting description according to first comment.
> Using -Declipse.projectNameTemplate is broken on multi module projects
> ----------------------------------------------------------------------
>
> Key: MECLIPSE-586
> URL: https://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="/moduleB"/>
> </classpath>
> moduleB/.project
> <projectDescription>
> <name>trunk-moduleB</name>
> [..]
> </projectDescription>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira