[MECLIPSE-364] incorrect dependencies with different projectNameTemplates in submodules

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4
• Fix Version/s: 2.6
• Component/s: Core : Dependencies resolution and build path (.classpath), Core : Multi-projects
• Environment: MacOSX, mvn 2.0.6
• Flags: Patch
• Assignee: Barrie Treloar
• Reporter: Frank Stolle
• Created: 31/Dec/07 07:44
• Updated: 05/Apr/15 14:43
• Resolved: 17/Dec/08 20:36

Description

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.