On Wed, Mar 10, 2010 at 3:09 AM, Simon Laws <[email protected]> wrote: > On Tue, Mar 9, 2010 at 10:23 AM, Simon Laws <[email protected]> wrote: >>>> >>> >>> I'd not deployed the latest OASIS assembly test runner jar, could you >>> try again now (you'll need to use mvn -U to pickup the new jar)? >>> >>> ...ant >>> >> >> Ah, splendid. Just re-run the tests and it's looking much better. >> >> Simon >> > > I've done a few edits so that only the tests that really fail are > commented out. > > In my build JCA_11004 fails here but doesn't in the old otest module. > Seems to be a problem with passing a Date in a JAXB object. > > Something else is a little odd in that the error properties files for > assembly are different here when compared to the one in the otest > module. I've got them as close as I can but it seems that the tests in > compliance-tests are behaving slightly differently that they do > directly from OASIS. Haven't got to the bottom of it yet. > > Simon >
The difference between the old otest setup and the tests in trunk is that the trunk ones use the JDK XML parser and the otests using Woodstox. That was also causing POL_4013 and POL_4028 to fail. I've added the Woodstox impl dependency to the trunk policy tests and POL_4013 passes but POL_4028 gets further but still fails for me but it does in the otests for me too. I'll try adding woodstox to the JCA tests to see if that fixes JCA_110004 too, though it would be good to fully understand why these are failing and try to fix it or at least document what the restrictions are when using the Sun JDK. ...ant
