Did set the release date for the 1.1.2 release in JIRA

to 2016-10-31 Did slip through somehow. It's on the dist svn folder, so all the other stuff is fine. LieGrue, strub

[jira] [Resolved] (BVAL-153) Upgrade OWB and Arquillian

[ https://issues.apache.org/jira/browse/BVAL-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved BVAL-153. Resolution: Fixed > Upgrade OWB and Arquillian > -- > > Key:

[jira] [Created] (BVAL-153) Upgrade OWB and Arquillian

Mark Struberg created BVAL-153: -- Summary: Upgrade OWB and Arquillian Key: BVAL-153 URL: https://issues.apache.org/jira/browse/BVAL-153 Project: BVal Issue Type: Task Components: tck

Re: build fails with OWB-1.7.3 and later

Oki, think I found the problem. In a refactoring I seem to have trashed the OWB Arquillian OwbSWClassLoader. It currently does return new URL(null, "archive:" + nodes.iterator().next()); But should really be return new URL(null, "archive:" + node, new ArchiveStreamHandler()) Will be fixed in

Re: build fails with OWB-1.7.3 and later

Currently using 2 boxes in parallel to spot the differences. It seems that in ValidationParser#applyConfigWithInstantiation the xmlConfig is null with OWB-1.7.3 and above. No idea why yet ... LieGrue,strub On Monday, 10 July 2017, 10:28:26 CEST, Romain Manni-Bucau

Re: build fails with OWB-1.7.3 and later

Ok, recall having done most of the setup so shout if you need me to reopen it ;) Le 10 juil. 2017 10:22, "Mark Struberg" a écrit : > Hi folks! > > BVal currently uses OWB-1.6.0 for the TCK. All works fine up to until > OWB-1.7.2, but from 1.7.3 up it fails. > I've now

build fails with OWB-1.7.3 and later

Hi folks! BVal currently uses OWB-1.6.0 for the TCK. All works fine up to until OWB-1.7.2, but from 1.7.3 up it fails. I've now checked a few tests and I'm quite confused. For example in MessageInterpolatorSpecifiedInValidationXmlNoDefaultConstructorTest The config file