Andy,
Apparently, your project had stale .class files in target/classes
directory and for some reasons maven considered them newer then their
respective sources. I cannot tell how you got into this state. Running
maven "clean" goal removed target directory and cleaned these state
files so now maven knows it needs to (re)compile the sources.
I assume everything works for you now, but please open a bug report with
sample project and steps to reproduce the problem if you find a
repeatable way to trigger this behaviour on purpose.
Andy Dingfelder wrote:
1. Does this project use "Maven Output Folders"?
It was not before, but I changed it to use this and it had no change
to the behavior of the compile issue.
2. What happens if you set goals to "clean install" in m2eclipse?
I have never run a different goal than just install. I tried "clean
install" and it first downloaded some jar files. Then it did croak on
my compile error.
Here is where it gets interesting:
I then tried and set the goal back to just "install" and it still
caught the error. I have to assume that the "cleaning" cleaned up
something that now allows the normal install step to catch the error?
Any insight into why it is now working would be appreciated
3. Does the build stops as expected if you run "mvn install" from
command line?
I am not running maven from the command line so I am not sure
inexactly what the steps would be to get this working. Since it is
working I assume I don't need to do this now?
Cheers,
Andy
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
