maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todor Todorov (JIRA)" <>
Subject [jira] Updated: (MECLIPSE-364) incorrect dependencies with different projectNameTemplates in submodules
Date Wed, 02 Apr 2008 11:45:59 GMT


Todor Todorov updated MECLIPSE-364:

    Attachment: maven-eclipse-plugin.patch

similar patch for maven-eclipse-plugin-2.5.1

> incorrect dependencies with different projectNameTemplates in submodules 
> -------------------------------------------------------------------------
>                 Key: MECLIPSE-364
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Dependencies resolution and build path, Core : Multi-projects
>    Affects Versions: 2.4
>         Environment: MacOSX, mvn 2.0.6
>            Reporter: Frank Stolle
>         Attachments: maven-eclipse-plugin.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:
For more information on JIRA, see:


View raw message