[MNG-2619] building from the middle pom of a (parent,child,grandchild) heirarchy fails

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-alpha-1, 2.0.4, 2.0.5
• Fix Version/s: 3.0-alpha-1
• Component/s: POM
• Flags: Patch
• Assignee: John Dennis Casey
• Reporter: Richard van der Hoff
• Created: 19/Oct/06 09:02
• Updated: 05/Apr/15 14:53
• Resolved: 01/Jun/07 17:31

Description

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.

Issue Links

• relates to: MNG-3057 properties not expanded in generated POMs when building A/B/C nested projects