On Tue, Jul 5, 2011 at 2:48 PM, Carsten Ziegeler <[email protected]> wrote: > No, it's not really a cycle; it's a cycle if you just look at > groupId/artifactId - but not if you consider versions as well. API > depends on a released version of Commons Testing and it seems that the > CI Build uses the current build version instead of the one specified > in the pom.
Ah ok - I can reproduce the problem using Maven 2.2.1 locally. I have changed https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/ and 1.5 to use Maven 3.0.3 (was 2.2.1) and triggered new builds, let's see if those work. -Bertrand
