DO NOT REPLY [Bug 9296] New: - pathconvert should use default separators without targetos

[bu...@apache.org]

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

pathconvert should use default separators without targetos

           Summary: pathconvert should use default separators without
                    targetos
           Product: Ant
           Version: 1.5Beta1
          Platform: All
               URL: http://jakarta.apache.org/ant/manual/CoreTasks/pathconve
                    rt.html
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: jozart@csi.com


I suggest that pathconvert not require targetos, even when neither filesep
nor pathsep is specified.

If no attributes are specified, it seems obvious what pathconvert should do:

 <pathconvert pathsep="${path.separator}"
              filesep="${file.separator}"
              property="foo" refid="bar"/>

If, say, I'm trying to convert a path to a string in order to supply a
cmd line arg to preverify.exe (j2me), why should I be forced to specify
the os?

Note, too, that the documentation is misleading concerning the filesep and
pathsep defaults.

1. filesep defaults to current JVM "File.separator"

=> Should read "file.separator"?

(Referring to a global property is more useful
than referring to a variable of the File class...)

2. pathsep defaults to current JVM "File.pathSeparator"

=> Should read "path.separator"?

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