I'm in the process of checking whether or not a clean build with 2.0.5fails. It is running as we speak.
Just a note with 2.0.6: "mvn clean install" fails "mvn clean compile" succeeds "mvn clean compile" and then "mvn install" succeeds. Henrique's observation seems to be valid for my build as well. My build consists of a combination of EJBs, WARs, JARs and EARs. It is always an EJB which breaks my build. One thing I am going to try before attaching an extended (-X) build log is to run the build while updating all plugins and snapshot (-up -U) just to make sure I am up to date with all plugins. The only nasty part, my build takes 30 minutes for a full run, so give me a few hours. Jeroen On 04/04/07, franz see <[EMAIL PROTECTED]> wrote:
Good day, My suggestion is to do a mvn clean first before compile or install ( to narrow down the problem )...i.e. mvn clean compile, mvn clean install. If doing both mvn clean compile and mvn clean install fails, then I guess it was working awhile ago due to some files produced by a previous built. However, if mvn clean compile still works while mvn clena install still fails, then I would like to ask for the build output :) Thanks, Franz Henrique Prange wrote: > > Hi Jeroen, > > I have a similar problem here. It appears only if I have a submodule A > referencing another submodule B and try "mvn install" on parent. The > submodule A cannot find the classes from B. If I do a "mvn install" on > submodule A, it works. > > I tried "mvn compile" on parent, as you described, and surprisingly it > works. > > Everything works fine with Maven 2.0.5. > > Cheers, > > Henrique > > Jeroen Leenarts wrote: >> 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 >> > > -- > > \o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda > | Phone: 55-21-2710-0178 E-mail: [EMAIL PROTECTED] > / \ http://www.moleque.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Compile-fails-during-install%2C-while-running-compile-succeeds-tf3525908s177.html#a9839120 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
