[
http://jira.codehaus.org/browse/MNG-2619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89549
]
Barrett Nuzum commented on MNG-2619:
------------------------------------
Seems to be related to repository metadata --
if the parent has been deployed rather than installed, it is more easily found.
> building from the middle pom of a (parent,child,grandchild) heirarchy fails
> ---------------------------------------------------------------------------
>
> Key: MNG-2619
> URL: http://jira.codehaus.org/browse/MNG-2619
> Project: Maven 2
> Issue Type: Bug
> Components: POM
> Affects Versions: 2.0.4, 2.0.5, 2.1
> Reporter: Richard van der Hoff
> Attachments: maven-project-middlepom.patch
>
>
> Given a heirerchy of projects - parent, child, grandchild - with <parent> and
> <module> links between them in the normal way:
> Attempting to start a build from the middle of the heirarchy - ie, the
> "child" - causes maven to attempt to download the parent from the repository
> - even if the version in the filesystem is correct in terms of
> {artifact,group,version}.
> The problem appears to be that the ProjectBuilder first reads the child pom,
> and caches the result (but not the parent pom). The reactor then makes the
> ProjectBuilder read the grandchild pom, and hence the child pom (which now
> comes from the cache), and the parent pom (which it can't find).
> This is much easier demonstrated than explained :/
> The attached patch fixes the problem by making sure that all the projects in
> the heirarchy (including the parent) are added to the cache. It also includes
> a test case to demonstrate the problem.
--
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
