Personally, I've never seen activemq run into duplicate classes in this way. I'll attempt the build with the same options and see if I can reproduce it locally.
Note that the "-fae" option allows us to get all of the tests run even when there is a failure because ActiveMQ has been notorious for tests that fail intermittently. Without the "-fae" you could run the build many times and never reach the end even with different tests failing on each run. Another thing that would be good to check - search the build directory for all *.java and *.class files for the reported duplicates. That might help us to track down from where they are being introduced. -- View this message in context: http://activemq.2283324.n4.nabble.com/Compile-failure-tp4703382p4703458.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
