[CONTINUUM-330] POM-only projects ignored. Causes problems with parent/child module pattern

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0-alpha-4
• Fix Version/s: 1.0
• Assignee: Emmanuel Venisse
• Reporter: A.J. Whitney
• Created: 03/Oct/05 19:28
• Updated: 13/Mar/06 04:05
• Resolved: 19/Oct/05 11:39

Description

POM-only projects are ignored. This poses problems for projects which depend on the POM-only project.

A common pattern is to have a POM-only parent with modules. This pattern is broken for two reasons:

1) The POM-only project is never added to Continuum so there is no way for the parent project to exist in the repository if Continuum is the only build mechanism (which seems likely for a production environment based on Continuum)

2) Each child module is added to Continuum separately and the parent/child module directory structure is not maintained. This is a problem as child modules cannot depend on the parent POM via directory structure (either the default ../pom.xml or via another path specified via the <relativePath> element).

As this parent/child module pattern is extremely common for all but trivial projects, this seems like an issue with a broad impact.

Issue Links

• is depended upon by: CONTINUUM-354 Need a way to poll for new projects
• relates to: CONTINUUM-176 adding parent pom create duplicate continuum projects for all children