[
https://issues.apache.org/jira/browse/VFS-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Eckenfels resolved VFS-549.
---------------------------------
Resolution: Fixed
Assignee: Bernd Eckenfels
Fix Version/s: 2.1
Thanks Sebb, committed as:
http://svn.apache.org/viewvc?view=revision&revision=1704931
> Replace System.getProperty("file|path.separator") with
> File.separator|pathSeparator
> -----------------------------------------------------------------------------------
>
> Key: VFS-549
> URL: https://issues.apache.org/jira/browse/VFS-549
> Project: Commons VFS
> Issue Type: Improvement
> Reporter: Sebb
> Assignee: Bernd Eckenfels
> Priority: Minor
> Fix For: 2.1
>
> Attachments: VER-549.patch
>
>
> The file separator character is available from both File.separator and
> System.getProperty("file.separator").
> The former is guaranteed to be a string of length 1, but the latter can be
> defined as a longer string on the Java command line. Thus the two can be
> different, but still allow the JVM to start up.
> I found the following worked:
> java -Dfile.separator=/xyz
> for Unix or the equivalent \xyz on Windows.
> [Using a different first character does not work - the JVM usually throws an
> exception as it cannot find some required files if the sep. is incorrect.]
> It looks like only the first character of the property is used by the JVM.
> However, this is not done by the application code I have seen, which means
> that there could be a discrepancy between the two methods.
> File.separator has the additional benefit that it is not subject to a
> privilege
> check.
> The same reasoning applies to "path.separator" => File.pathSeparator
> Commons code should always use the File constants.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
