You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Maarten Coene <ma...@yahoo.com> on 2011/01/22 13:43:34 UTC
failing ivy tests on gump
Hi,
the Ivy junit tests suddenly failed with the error below.
Any ideas?
Provider org.apache.xalan.processor.TransformerFactoryImpl not found"
type="javax.xml.transform.TransformerFactoryConfigurationError">javax.xml.transform.TransformerFactoryConfigurationError:
Provider org.apache.xalan.processor.TransformerFactoryImpl not found
at javax.xml.transform.TransformerFactory.newInstance(Unknown Source)
at
org.apache.ivy.ant.IvyArtifactReport.createTransformerHandler(IvyArtifactReport.java:194)
at org.apache.ivy.ant.IvyArtifactReport.generateXml(IvyArtifactReport.java:138)
at org.apache.ivy.ant.IvyArtifactReport.doExecute(IvyArtifactReport.java:124)
at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277)
at
org.apache.ivy.ant.IvyArtifactReportTest.testSimple(IvyArtifactReportTest.java:63)
regards,
Maarten
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: failing ivy tests on gump
Posted by Stefan Bodewig <bo...@apache.org>.
On 2011-01-23, Maarten Coene wrote:
> maybe a stupid question, but isn't it caused because xml-apis is
> prepended to the boothclasspath instead of appended?
this is necessary to make the Java VM use Gump's versions of xml-apis,
Xerces and Xalan - Gump's way to avoid the "endorsed standards"
mechanism.
This has been the case for Gump for years. What has changed is Ant and
that everything that is on the bootclasspath for Ant now also ends up on
the bootclasspath of the forked VM (albeit using -Xbootclasspath without
/p or /a).
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: failing ivy tests on gump
Posted by Maarten Coene <ma...@yahoo.com>.
Stefan,
maybe a stupid question, but isn't it caused because xml-apis is prepended to
the boothclasspath instead of appended?
Maarten
----- Original Message ----
From: Stefan Bodewig <bo...@apache.org>
To: general@gump.apache.org
Sent: Sun, January 23, 2011 7:47:43 AM
Subject: Re: failing ivy tests on gump
On 2011-01-22, Maarten Coene wrote:
> the Ivy junit tests suddenly failed with the error below.
> Any ideas?
It is my change to Ant which makes build.sysclasspath apply to the
bootclasspath of a forked VM and ivy-test is not the only one affected
(xmlunit, log4j's tests and test-ant fail for the same reason, I guess).
In Ivy's case the tests now have xml-apis.jar on their bootclasspath but
not xalan and xml-apis.jar requires Xalan as TraX processor.
xml-apis and xerces get into ivy-test's bootclasspath via commons-vfs
(which has optional dependencies on them) and
<depend project="commons-vfs" inherit="all" />
in ivy-test's descriptor. I see two options to fix this and will leave
it to you to decide (i.e. I won't touch anything):
(1) explicitly add a dependency on Xalan to ivy-test
(2) remove the inherit="all" from the dependency and add explicit
dependency elements for vfs' dependencies actually required to run the
tests.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: failing ivy tests on gump
Posted by Stefan Bodewig <bo...@apache.org>.
On 2011-01-22, Maarten Coene wrote:
> the Ivy junit tests suddenly failed with the error below.
> Any ideas?
It is my change to Ant which makes build.sysclasspath apply to the
bootclasspath of a forked VM and ivy-test is not the only one affected
(xmlunit, log4j's tests and test-ant fail for the same reason, I guess).
In Ivy's case the tests now have xml-apis.jar on their bootclasspath but
not xalan and xml-apis.jar requires Xalan as TraX processor.
xml-apis and xerces get into ivy-test's bootclasspath via commons-vfs
(which has optional dependencies on them) and
<depend project="commons-vfs" inherit="all" />
in ivy-test's descriptor. I see two options to fix this and will leave
it to you to decide (i.e. I won't touch anything):
(1) explicitly add a dependency on Xalan to ivy-test
(2) remove the inherit="all" from the dependency and add explicit
dependency elements for vfs' dependencies actually required to run the
tests.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org