Actually, that sounds pretty close to my experience with using Maven2 so far.
Everything is a SNAPSHOT still (so you end up downloading it and marking it "beta" in your own repos). Lots of poorly maintained POMs (so you get all sorts of dependencies you don't need). Projects that depend on repositories that go up and down like waves. Continuum and Archiva projects that haven't seen upgrades in over a year. Archiva not even being close to a stable product--even though all their docs talk about it like it exists already. Maven releases that cause more bugs than they fix (and a dev team that could care less). Maven is a great idea. Whatever happened to take all the steam out of it makes one wonder about possibly just forking it. Or waiting for Atlassian to release their own take on it. Sorry for the rant, but this just arrived as I'm trying to fix the now broken WebDAV deployment in 2.0.6 (which I was upgrading to because I need one of the fixes included in 2.0.6). Unfortunately, duct tape and staples are pretty much the day to day of Maven practices. sw -----Original Message----- From: Barrett Nuzum [mailto:[EMAIL PROTECTED] Sent: Monday, April 16, 2007 6:26 PM To: [email protected] Subject: [mojo-dev] Aspectj-maven-plugin release and/or abandonment? 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 --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
