Some tests fail when we use Crimson (i.e. JDK 1.4)

[Stefan Bodewig <bo...@apache.org>]

... expect the first Gump nag mail in about three hours 8-)

After I've added test-ant-no-xerces we find some places where we are
either Xerces centric or expect things to work where Crimson isn't
good enough.

The whole project passed on JDK 1.5, so we are pretty save there.

Things failing on plain JDK 1.4 are:

* org.apache.tools.ant.IncludeTest

handling of relative URIs seems to be broken.

* org.apache.tools.ant.taskdefs.optional.SchemaValidateTest

well, Crimson doesn't support XSD.

Is there any way to detect whether a parser supports XSD from within
the build file and skip the test?

Should the test pass gracefully?

* org.apache.tools.ant.taskdefs.optional.XmlValidateTest

same as above.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org

Re: Some tests fail when we use Crimson (i.e. JDK 1.4)

[Steve Loughran <st...@apache.org>]

Stefan Bodewig wrote:

> 
> * org.apache.tools.ant.taskdefs.optional.SchemaValidateTest
> 
> well, Crimson doesn't support XSD.
> 
> Is there any way to detect whether a parser supports XSD from within
> the build file and skip the test?
> 
> Should the test pass gracefully?
> 
> * org.apache.tools.ant.taskdefs.optional.XmlValidateTest
> 


We can find this by setting the appropriate features in the parser and 
looking for errors.  Easy to do in code, not from in ant.

Maybe we could have a <parsersupports /> condition that lets you set a 
feature/property to a value, if there is felt to be broad need for the 
feature?

otherwise, add some logic in each test that uses schema stuff.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org