[jira] (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:comment-tabpanel&focusedCommentId=322705#comment-322705 ] Patrik Martinovský edited comment on MECLIPSE-586 at 3/26/13 3:25 PM: -- MNG-586,634-maven-eclipse-plugin.patch: if eclipse.projectNameTemplate is specified on the command line it takes precedence over xml plugin configuration for dependent maven projects... was (Author: martinovsky): if eclipse.projectNameTemplate is specified on the command line it takes precedence over xml plugin configuration for dependent maven projects... > 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 > Attachments: MNG-586,634-maven-eclipse-plugin.patch > > > 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 > > trunk-moduleA > > moduleB > > [..] > > moduleA/.classpath > > [..] > > > moduleB/.project > > trunk-moduleB > [..] > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (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 ] Patrik Martinovský updated MECLIPSE-586: Attachment: MNG-586,634-maven-eclipse-plugin.patch if eclipse.projectNameTemplate is specified on the command line it takes precedence over xml plugin configuration for dependent maven projects... > 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 > Attachments: MNG-586,634-maven-eclipse-plugin.patch > > > 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 > > trunk-moduleA > > moduleB > > [..] > > moduleA/.classpath > > [..] > > > moduleB/.project > > trunk-moduleB > [..] > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (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:comment-tabpanel&focusedCommentId=294314#comment-294314
]
Max Bowsher commented on MECLIPSE-586:
--
This regression was introduced in r727620.
To fix, just delete the code which does the wrong thing from EclipsePlugin.java:
MavenProject reactorProject = getReactorProject( artifact );
if ( reactorProject != null )
{
return IdeUtils.getProjectName(
getProjectNameTemplateForMavenProject( reactorProject ), artifact );
}
> 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
>
> trunk-moduleA
>
> moduleB
>
> [..]
>
> moduleA/.classpath
>
> [..]
>
>
> moduleB/.project
>
> trunk-moduleB
> [..]
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
