[
http://jira.codehaus.org/browse/CONTINUUM-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wendy Smoak closed CONTINUUM-1210.
----------------------------------
Assignee: Wendy Smoak
Resolution: Incomplete
> Build order not correct
> -----------------------
>
> Key: CONTINUUM-1210
> URL: http://jira.codehaus.org/browse/CONTINUUM-1210
> Project: Continuum
> Issue Type: Bug
> Components: Core system
> Environment: SVN-build of Continuum (14/03/07), Maven 2.0.4
> Reporter: Stefan Seidel
> Assignee: Wendy Smoak
>
> Although quite a few JIRA issues here give the impression that the build
> order with continuum should be the same as in the M2 reactor, this is
> absolutely not true for us here.
> All of the modules are built in something like alphabethical order, but not
> quite - it's just strange and not very helpful.
> Our project is quite big (67 modules) and we use almost only version ranges,
> e.g. [1.0,2.0) - maybe it's that? The dependencies of the projects are being
> shown in the project view, example:
> {code}
> Group Id Artifact Id Version
> de.xpm.ejb common [1.0,2.0)
> commons-el commons-el [1.0,)
> javax.servlet jsp-api [1.0,)
> de.xpm xpm-portal-libs [1.0,2.0)
> de.xpm mock [1.0,2.0)
> de.xpm xpm-global-common [1.0,2.0)
> de.xpm xpm-portal-common [1.5,2.0)
> de.xpm.ejb rolesystem [1.0,2.0)
> de.xpm components [1.0,2.0)
> com.sun.faces jsf-impl 1.1
> javax.servlet jstl 1.1.2
> de.xpm.ejb shop [1.0,2.0)
> de.xpm.portlet Meta [1.0,2.0)
> jsfunit jsfunit 0.1.0
> {code}
--
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
