You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by Nick Burch <ni...@alfresco.com> on 2011/02/01 14:46:02 UTC

Re: [GUMP@vmgump]: Project poi-test (in module poi) failed (fwd)

Here's the latest from the gump team on the failure

---------- Forwarded message ----------
From: Stefan Bodewig <bo...@apache.org>
To: general@gump.apache.org
Cc: Nick Burch <ni...@alfresco.com>
Subject: Re: [GUMP@vmgump]: Project poi-test (in module poi) failed

On 2011-01-27, Stefan Bodewig wrote:
> When Ant forks a new VM like it does for forked JUnit tests it will now
> honor build.sysclasspath for the bootclasspath as well.  This means that
> some jars - in particular xml-apis, xalan and xerces - that used to be
> on Ant's bootclasspath but not the one of the forked VM will now be on
> the forked VM's bootclasspath as well.

OK, you used to get the XML parser that is part of the JDK in your tests
but now have the trunk version of Xerces.

<http://vmgump.apache.org/gump/public/poi/poi-test/gump_file/TEST-org.apache.poi.xssf.extractor.TestXSSFExportToXML.txt.html>

Either Xerces trunk has become more strict than the JDK parser or we
need to help the forked VM find the DTD or something like this.  Without
diving into the test I can't say for sure what is needed here.

Stefan

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