[
http://jira.codehaus.org/browse/CONTINUUM-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145888#action_145888
]
Napoleon Esmundo C. Ramirez commented on CONTINUUM-1850:
--------------------------------------------------------
So it seems that removing --non-recursive doesn't make sense in this kind of
structure.
There are lots of issues reporting the wrong build order of the projects in a
project group. Currently in Continuum's implementation, building all the
projects in a project group will queue the projects in the build queue, with
the order defined by the dependency relationships and by the build state. I'd
like to suggest using a persistent backing queue for a multi-module project
that is defined upon adding it in Continuum. This will serve as a backbone for
that group's build that will ensure that the build order will stay as it was at
the time it was added.
> 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
