continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Venisse (JIRA)" <>
Subject [jira] Closed: (CONTINUUM-330) POM-only projects ignored. Causes problems with parent/child module pattern
Date Wed, 19 Oct 2005 16:41:11 GMT
     [ ]
Emmanuel Venisse closed CONTINUUM-330:

      Assign To: Emmanuel Venisse
     Resolution: Fixed
    Fix Version: 1.0-beta-2

already fixed

> POM-only projects ignored.  Causes problems with parent/child module pattern
> ----------------------------------------------------------------------------
>          Key: CONTINUUM-330
>          URL:
>      Project: Continuum
>         Type: Bug
>     Versions: 1.0-alpha-4
>     Reporter: A.J. Whitney
>     Assignee: Emmanuel Venisse
>      Fix For: 1.0-beta-2

> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message