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/05/02 23:46:19 UTC

DO NOT REPLY [Bug 8756] New: - PathTokenizer on NetWare has tokenizing bug - AvailableTest 21 fails

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=8756>.
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=8756

PathTokenizer on NetWare has tokenizing bug - AvailableTest 21 fails

           Summary: PathTokenizer on NetWare has tokenizing bug -
                    AvailableTest 21 fails
           Product: Ant
           Version: 1.5Beta1
          Platform: Other
        OS/Version: Netware
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: jtulley@novell.com


taskdefs.AvailableTest, test 21 fails on NetWare.  It is trying to parse the 
XML attr - "classpath="${java.home}/lib/rt.jar:${java.home}/lib/classes.zip" 
(which is expanded to SYS:\JAVA/lib/rt.jar:SYS:\JAVA/lib/classes.zip)  It looks 
like this is a scenario that my parsing code in PathTokenizer doesn't take into 
account.  Even though PathTest.java tests a fairly extensive set of scenarios, 
it did not test this exact type of string.   I have the fix and some more 
PathTest.java enhancements that I will attach to this bug report.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>