You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2002/10/20 23:15:52 UTC
DO NOT REPLY [Bug 13800] New: -
C: names fail in XML expansion caused by xerxes
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13800>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13800
C: names fail in XML expansion caused by xerxes
Summary: C: names fail in XML expansion caused by xerxes
Product: Ant
Version: 1.1
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: Wrapper scripts
AssignedTo: ant-dev@jakarta.apache.org
ReportedBy: brianj@otterspace.com
We've got a custom task that uses XSLT, and the xercesImpl.jar is "first" in
the classpath because of the ant.bat file so it's being used...and IT throws a
fit with filenames that start with C:/, treating them as URL with protocol "C"
(which is correct--C:/ seems to be a protocl).
The "temp fix" to this is to REMOVE the file xercesImpl.jar from the %
ANT_HOME%/lib directory.
I don't know if this is an Ant problem, or a xerces problem, but it manifests
in the Ant custom build tag process if your custom process uses XSLT on Windows
platforms.
Is it still necessary to include xercesImpl at all with JDK 1.4 or greater?
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>