continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Napoleon Esmundo C. Ramirez (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1850) Build Failure with Multimodule project - with flat file structure
Date Fri, 22 Aug 2008 16:04:27 GMT


Napoleon Esmundo C. Ramirez commented on CONTINUUM-1850:

Building the parent project without the "--batch-mode --non-recursive" argument in the build
definition will fail as expected, because maven will look for <module>../module1</module>
that doesn't exist.  Though the submodules were checked out and added into continuum successfully,
those will not be related to the parent project--not just because the submodules weren't checked
out in the same scm tree as the parent (directories are named as project id's by continuum),
but also because the ProjectBuilder handles projects individually and isolated from each other
in a flat filesystem hierarchy.

And I really don't know if using that kind of project layout is a recommended practice.  It
even causes issues in the release, as stated in CONTINUUM-1569.  For me, I'd rather follow:

|   '--pom.xml
|   '--pom.xml
    '-- pom.xml

If not attainable in the filesystem, I'll do it in the scm via svn:externals just to form
that kind of layout.

Just my thoughts.

> Build Failure with Multimodule project - with flat file structure
> -----------------------------------------------------------------
>                 Key: CONTINUUM-1850
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>          Components: Core system
>    Affects Versions: 1.2
>            Reporter: Jevica Arianne B. Zurbano
> Building a multi-module project with flat file structure works fine in command line,
but when hosted in Continuum, it's failing.
> Project structure is:
>   parent-project
>     '-- pom.xml
>   module1
>     '-- pom.xml
>   module2
>     '-- pom.xml
>   module3
>     '-- pom.xml
> Modules are included in the parent-project\pom.xml.
> relativePath of parent-project is specified in the child POMs.
> This issue is related to

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