ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18352] New: - The filename and path of the build file that failed is printed out in URL encode format.
Date Wed, 26 Mar 2003 06:28:28 GMT
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=18352>.
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=18352

The filename and path of the build file that failed is printed out in URL encode format. 

           Summary: The filename and path of the build file that failed is
                    printed out in URL encode format.
           Product: Ant
           Version: 1.5.2
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: jpohto@cs.helsinki.fi


The filename and path of the build.xml file is printed out in URL encoded 
format. 

This seems to be a side-effect of the change to a new version of Xerces, since 
the SAXParserException.getSystemId() returns the SystemId in URL encoded format 
(which is correct bahaviour from the parser's point of view, I think). The 
problem basically is that the systemId is incorrectly assigned to the Location 
object to represent a filename.

The effect of this is that some software (eg. IDEs), that are using Ant, are 
not able to open the correct file when the build fails, because the filename is 
not actually a filename.

A workaround would be to parse the filename from the SystemId and to decode the 
escape characters.

Mime
View raw message