Hi Mojoers. We have been migrating a relatively complex CI environment to Maven2 over the past few months and are finally able to see the light at the end of the tunnel. We recently tried to start releasing projects, but needed to use the aspectj-maven-plugin v 1.0-beta-4 to be able to weave our aspects with our code. (Long story.) This version is, of course, a SNAPSHOT, and you can't depend on a snapshot plugin when releasing. Ouch. So we decided to try to check out the source code and fork a version of the snapshot so that we could release. The project would not compile without Java 1.5, even though the POM specifies compiler target and source 1.4. Even then, we had a number of test failures, (when removing the offending Java 1.5 code) straight from the start. We're stuck on Java 1.4.2 (and IBM JDK, natch) for a while longer, so this is not good for us. I figured that maybe the code was just broken at the time that I checked it out, and attempted to visit Codehaus' CI environment, but can't access *any* of them (http://maestro.ci.codehaus.org/). I always get either a timeout or HTTP error from a proxy. (CruiseControl, Beetlejuice, Bamboo, and Continuum all do the same.) We've duct taped and stapled the existing binary and metadata into a team repo from snapshots.repository.codehaus.org, but the experience and solution seemed pretty far from Maven practices. Thought you'd might like to know. Barrett :: Barrett Nuzum Consultant, Skill Development Direct: 918.640.4414 Fax: 972.789.1340
Valtech Technologies, Inc. 5080 Spectrum Drive Suite 700 West Addison, Texas 75001 www.valtech.com <http://www.valtech.com/> making IT business friendly --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
