[MNG-4705] parent pom doesn't get resolved if it is contained in a submodule

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 3.0-beta-1
• Component/s: Reactor and Workspace
• Assignee: Benjamin Bentmann
• Reporter: Mark Struberg
• Created: 10/Jun/10 09:16
• Updated: 10/Jun/10 09:20
• Resolved: 10/Jun/10 09:20

Description

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.