You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/06/10 16:22:12 UTC
[jira] Closed: (MNG-4705) parent pom doesn't get resolved if it is
contained in a submodule
[ http://jira.codehaus.org/browse/MNG-4705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MNG-4705.
----------------------------------
Resolution: Not A Bug
Assignee: Benjamin Bentmann
The POMs are missing the proper {{<relativePath>}} specs for Maven to resolve the parents.
> parent pom doesn't get resolved if it is contained in a submodule
> -----------------------------------------------------------------
>
> Key: MNG-4705
> URL: http://jira.codehaus.org/browse/MNG-4705
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Reactor and workspace
> Affects Versions: 3.0-beta-1
> Reporter: Mark Struberg
> Assignee: Benjamin Bentmann
> Attachments: reactorbug-testprj.zip
>
>
> I have the following situation in my project which used to work in maven 2.x (2.0.9, 2.1.1):
> I have a 'parents' module with subprojects for frontend, backend etc. Those contain only parent poms containing common settings for these kind of projects
> The real frontend wars and backend jars are in separate modules for own areas which reference the apropriate frontend-parent or backend-parent from the parents module.
> This works well in maven2 but fails to resolve the parent poms in 3.0-beta-1
> The attached sample project will show the problems.
--
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