[
http://jira.codehaus.org/browse/CONTINUUM-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145756#action_145756
]
nramirez edited comment on CONTINUUM-1850 at 8/22/08 11:05 AM:
----------------------------------------------------------------------------------
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:
{noformat}
project
|--pom.xml
|--module1
| '--pom.xml
|--module2
| '--pom.xml
'--module3
'-- pom.xml
{noformat}
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.
Nap
was (Author: nramirez):
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:
project
|--pom.xml
|--module1
| '--pom.xml
|--module2
| '--pom.xml
'--module3
'-- 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.
Nap
> Build Failure with Multimodule project - with flat file structure
> -----------------------------------------------------------------
>
> Key: CONTINUUM-1850
> URL: http://jira.codehaus.org/browse/CONTINUUM-1850
> 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 http://jira.codehaus.org/browse/CONTINUUM-1569.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
