Yes, we need a global ordering, so projects will be build independently of groups, because in some
case a cycle can be created between groups (not necessary between projects).
In case a cycle is detected between projects, continuum can't find the build order. In this case, I
think we need to
the issue isn't cycles within a normal m2 build, but when you shove 4
or 5 of them together into one continuum instance and then ask them
all to play together.
For example if you shoved continuum, maven-shared and archiva all into
the same continuum instance and triggered a build with all of
Can you do the same with javax.activation? :)
[EMAIL PROTECTED] wrote:
Author: jmcconnell
Date: Wed Nov 8 09:17:12 2006
New Revision: 472550
URL: http://svn.apache.org/viewvc?view=revrev=472550
Log:
align with latest plexus-security configuration mechanism
update the pom.xml with a
On 09/11/2006, at 4:17 AM, [EMAIL PROTECTED] wrote:
+!--
dependency
groupIdorg.apache.derby/groupId
artifactIdderby/artifactId
/dependency
+--
+dependency
+ groupIdpostgresql/groupId
+ artifactIdpostgresql/artifactId
+
