Wayne Fay wrote > Would be great if you could switch back to 3.0 and try again, then > report back with the error details (ideally with a small sample) so it > can be looked into and resolved if it is a problem/bug.
Just responded to Anders with details of additional testing. Bottom line, 3.0 works for me single-threaded, or multithreaded when *forceJavacCompilerUse* is true, but fails otherwise. Unfortunately my small sample wasn't able to reproduce the problem. My hunch is that our combination of a large project (~150 modules) & multi-threading (-T 2C on a 24-way box) is exposing a problem that a "small" sample wouldn't expose. -- View this message in context: http://maven.40175.n5.nabble.com/What-s-new-in-maven-compiler-plugin-3-0-tp5738129p5738311.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
