I'm not able to reproduce any of this in master so far. I hesitate to say "since the upgrade" as I did not try the code before and see it fail and also that both buildbot and Jenkins still see issues.
I attempted to setup a Jenkins job for us, but at first glance it looks like the reactor order is completely wrong. - https://builds.apache.org/job/TomEE/4/ It does have the NoClassDefFound bval failures though, so maybe it's good. -- David Blevins http://twitter.com/dblevins http://www.tomitribe.com > On Aug 15, 2019, at 8:23 AM, Jean-Louis Monteiro <[email protected]> > wrote: > > Hi, > > I was updating the build with some fixes for Java 11, but I can't get a > green build anymore. > Looks like BVal TCK are failing with a weird NoClassDefFound. > > There have been a lot of discussions around BVal, so not sure if that is > related. > We currently downgraded to 2.0.0 > > The failures are > >> [ERROR] Failures: >> [ERROR] >> DuplicateConfigurationTest>Arquillian.run:164->testXmlConfiguredConstraintExposesCorrespondingAnnotationViaMetadata:72 >> » Validation >> [ERROR] >> XmlConfigurationTest>Arquillian.run:164->testAnnotationDefinedConstraintApplies:176->AbstractTCKTest.getValidator:61 >> » Validation >> [ERROR] >> XmlConfigurationTest>Arquillian.run:164->testCascadingConfiguredInXml:203->AbstractTCKTest.getValidator:61 >> » Validation >> [ERROR] >> XmlConfigurationTest>Arquillian.run:164->testClassConstraintDefinedInXml:79->AbstractTCKTest.getValidator:61 >> » Validation >> [ERROR] >> XmlConfigurationTest>Arquillian.run:164->testElementConversionInXmlConfiguredConstraint:255->AbstractTCKTest.getValidator:61 >> » Validation >> [ERROR] >> XmlConfigurationTest>Arquillian.run:164->testFieldConstraintDefinedInXml:151->AbstractTCKTest.getValidator:61 >> » Validation >> [ERROR] >> XmlConfigurationTest>Arquillian.run:164->testIgnoreValidationXml:109->AbstractTCKTest.getValidator:61 >> » Validation >> [ERROR] >> XmlConfigurationTest>Arquillian.run:164->testMappingFilesAddedViaConfigurationGetAddedToXmlConfiguredMappings:216->AbstractTCKTest.getValidator:61 >> » Validation >> [ERROR] >> XmlConfigurationTest>Arquillian.run:164->testPropertyConstraintDefinedInXml:127->AbstractTCKTest.getValidator:61 >> » Validation >> [ERROR] >> XmlConfiguredConstraintValidatorTest>Arquillian.run:164->testExcludeExistingValidators:57 >> » Validation >> [ERROR] >> XmlConfiguredConstraintValidatorTest>Arquillian.run:164->testIncludeExistingValidators:84 >> » Validation >> > > The cause is > > Caused by: java.lang.ClassNotFoundException: >> org.hibernate.beanvalidation.tck.tests.xmlconfiguration.ConsistentUserInformation >> at java.net.URLClassLoader.findClass(URLClassLoader.java:382) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:424) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:357) >> at java.lang.Class.forName0(Native Method) >> at java.lang.Class.forName(Class.java:348) >> at >> org.apache.bval.jsr.xml.ValidationMappingParser.__privileged_org_apache_bval_util_reflection_Reflection$$toClass(ValidationMappingParser.java) >> at >> org.apache.bval.jsr.xml.ValidationMappingParser.__privileged_org_apache_bval_util_reflection_Reflection$$toClass(ValidationMappingParser.java) >> at >> org.apache.bval.jsr.xml.ValidationMappingParser.org_apache_bval_util_reflection_Reflection$$toClass(ValidationMappingParser.java) >> at >> org.apache.bval.jsr.xml.ValidationMappingParser.loadClass(ValidationMappingParser.java:163) >> > > Obviously I checked the archive created by the TCK and the class is in > there. > So looks like BVal is not able to see that class in the arquillian archive > created. > > Anyway, thoughts are welcome. > > BTW, I tried upgrading to 2.0.2 and it's the same, so it might be related > with changes I made. > I will continue to look at this issue > > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com
