I'm not sure how to debug this, but this is what happened after having upgraded to Maven 2.0.6. I have checked my dependency management sections as described in the release notes. No conflicts there.
1. Get a fresh code base. 2. When I run "mvn install" the build fails during the compile phase of a project. 3. While running "mvn compile" always succeeds on the same set of source files. 4. Running "mvn install" again results in a successful build. 5. Running "mvn clean install" again results in a failure during the compile phase. Seems like a problem I should be capable of narrowing down, right? Well, the thing is, the compile can fail and abort maven 2 at several different projects. I've tried running with the -X option and diff-ed the relevant sections of output. Nothing there. Anybody got any clues what could cause such behavior? Or even how I might debug this? In my opinion running "mvn install" or "mvn compile" followed by "mvn install" should make no difference. Install requires passing the install phase. Regards, Jeroen
