[ http://jira.codehaus.org/browse/MECLIPSE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on MECLIPSE-364 started by Barrie Treloar. > incorrect dependencies with different projectNameTemplates in submodules > ------------------------------------------------------------------------- > > Key: MECLIPSE-364 > URL: http://jira.codehaus.org/browse/MECLIPSE-364 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : Dependencies resolution and build path > (.classpath), Core : Multi-projects > Affects Versions: 2.4 > Environment: MacOSX, mvn 2.0.6 > Reporter: Frank Stolle > Assignee: Barrie Treloar > Fix For: 2.6 > > Attachments: maven-eclipse-plugin.patch, > maven-eclipse-plugin.test.patch, patch.txt > > > If you have a project with different submodules and you use different > projectNameTemplate-Settings in some modules, the resulting .project and > .classpath -Files contains wrong project-names, because the wrong > template-name will be applied. > Example: > A > +---B (with projectNameTemplate "b-[artifactId]") > +---C (with projectNameTemplate "c-[artifactId]") > And C depends on B. In C the dependency will result in project c-B and not > b-B, as suspected. > A testcase is currently not submitted, because I don't know how to check > files in sub-projects. Only the expected-directory of the main-project will > be checked. -- 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