Anders Hammar wrote > OK, looks like a bug. Would be very good if you could reproduce this so it > could get fixed.
I was able to confirm a few things: 1) Multi-threaded (-T 2C) builds with compiler plugin 3.0 consistently fail when *forceJavacCompilerUse* is false. 2) Single-threaded builds with compiler plugin 3.0 work fine when *forceJavacCompilerUse* is false. 3) Multi-threaded builds with compiler plugin 3.0 work fine when *forceJavacCompilerUse* is true. I wish I could put together a simple test case to demonstrate the issue but unfortunately I can't share the code where I am seeing the problem. Hopefully the above will yield some clues. Other potentially pertinent info: *> java -version* java version "1.6.0" Java(TM) SE Runtime Environment (build pxa6460sr10-20111208_01(SR10)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr10-20111207_96808 (JIT enabled, AOT enabled) J9VM - 20111207_096808 JIT - r9_20111107_21307ifx1 GC - 20110519_AA) JCL - 20111104_02 *> uname -a* Linux REDACTED 2.6.32-220.7.1.el6.x86_64 #1 SMP Fri Feb 10 15:22:22 EST 2012 x86_64 x86_64 x86_64 GNU/Linux *> cat /proc/cpuinfo | grep processor | wc -l* 24 -- View this message in context: http://maven.40175.n5.nabble.com/What-s-new-in-maven-compiler-plugin-3-0-tp5738129p5738310.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
