On 06/20/2012 01:15 PM, David Bosschaert wrote: > I decided to clean up my local Maven repo and rebuild AS7 after that. > Running mvn install on master fails in the messaging subsystem with: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile > (default-testCompile) on project jboss-as-messaging: Compilation > failure: Compilation failure: > [ERROR] > /Users/david/clones/bosschaert_jboss-as_020512/messaging/src/test/java/org/jboss/as/messaging/test/SubsystemDescriptionsUnitTestCase.java:[31,29] > cannot find symbol > [ERROR] symbol : class MessagingExtension > [ERROR] location: package org.jboss.as.messaging > > Anyone an idea why? I also had to wipe my local maven repo and I had similar errors. Looking at maven output, some of the jars that were downloaded again were corrupted. Removing them again to force download fixed that. jeff

On 20/06/2012 15:11, Scott Marlow wrote: > On 06/20/2012 09:27 AM, Jeff Mesnil wrote: >> On 06/20/2012 01:15 PM, David Bosschaert wrote: >>> I decided to clean up my local Maven repo and rebuild AS7 after that. >>> Running mvn install on master fails in the messaging subsystem with: >>> >>> [ERROR] Failed to execute goal >>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile >>> (default-testCompile) on project jboss-as-messaging: Compilation >>> failure: Compilation failure: >>> [ERROR] >>> /Users/david/clones/bosschaert_jboss-as_020512/messaging/src/test/java/org/jboss/as/messaging/test/SubsystemDescriptionsUnitTestCase.java:[31,29] >>> >>> cannot find symbol >>> [ERROR] symbol : class MessagingExtension >>> [ERROR] location: package org.jboss.as.messaging >>> >>> Anyone an idea why? >> >> I also had to wipe my local maven repo and I had similar errors. Looking >> at maven output, some of the jars that were downloaded again were >> corrupted. Removing them again to force download fixed that. >> >> jeff >> > > There is a maven option to check if the http get failed: > > -C,--strict-checksums Fail the build if checksums don't match > Yes after wiping out my repo again and rebuilding everything was good, so I guess it was a badly downloaded jar. I'm a little surprised about this though as normally it fails more horribly if your artifacts are corrupt while here it's complaining about a missing class, no other badness reported...