On Jul 9, 2010, at 1:45 PM, Donald Woods wrote: > I just did a "mvn clean install" from the project root and hit the > problem. Seems that there were changes in return types in - > bval-jsr303/src/main/java/org/apache/bval/jsr303/ApacheFactoryContext.java > that is now causing the bval-xstream to be required, instead of > optional. I redo the changes in BVAL-77 to fix this. >
I just saw that I had caused that. Sorry about that. :/ -Matt > > -Donald > > > On 7/9/10 2:31 PM, Matt Benson wrote: >> >> On Jul 9, 2010, at 1:26 PM, Donald Woods wrote: >> >>> Well, these look like valid failuresin bval-guice due to recent changes >>> (I can recreate on my Mac with 1.6.0_20)... All 4 failures have the >>> same cause - >>> >> >> Weird, because I'm running 'mvn test' from bval/ and get full success. What >> command line are you using to recreate the problem? When I went out to >> Hudson I saw those "error parsing repository.xml" errors that you had >> reported to the builds list last month, so assumed that was the reason the >> dependency class wasn't found. >> >> Regards, >> Matt >> >>> Error injecting constructor, java.lang.NoClassDefFoundError: >>> org/apache/bval/xml/XMLMetaBeanManager >>> at >>> org.apache.bval.guice.ValidatorProvider.<init>(ValidatorProvider.java:45) >>> while locating org.apache.bval.guice.ValidatorProvider >>> while locating javax.validation.Validator >>> for field at >>> org.apache.bval.guice.ValidateMethodInterceptor.validator(ValidateMethodInterceptor.java:53) >>> at >>> org.apache.bval.guice.ValidationModule.configure(ValidationModule.java:60) >>> >>> >>> On 7/9/10 1:47 PM, Matt Benson wrote: >>>> I see this has happened before; anyone know what fixes it? :| >>>> >>>> -Matt >>>> >>>> On Jul 9, 2010, at 12:43 PM, Apache Hudson Server wrote: >>>> >>>>> See >>>>> <http://hudson.zones.apache.org/hudson/job/BeanValidation-trunk-windows/changes> >>>>> >>>>> >>>> >>>> >> >>
