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
Ok, I've got an interesting problem on my hands. I've just checked with our
compliancy officer and I am not allowed to post the output on the
internet. The risks of anonymizing and missing something is too great. (Log
file of over 600KiB.) I can understand the reasoning, because it would
provide
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
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,
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
