JDK-4164823 : java.io.File.getCanonicalPath still does not handle drive-relative paths (win32)
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.io
  • Affected Version: 1.2.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 1998-08-08
  • Updated: 1999-01-15
  • Resolved: 1999-01-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.2.0 1.2fcsFixed
Related Reports
Relates :  
JDK-4070044 - java.io.File.getCanonicalPath does not handle drive-relative paths (win32)
Description
The regression test written for 4070044, which originally reported this bug, is
now failing.  The getCanonicalPath method works fine as long as the current
directory of the drive in the input path is the root directory, but if not then
it fails to insert a separator between the directory and the filename.  For
example, if the current directory of the C: drive is \foo\bar, then the
canonical path of C:baz is computed as C:\foo\barbaz when it should be
C:\foo\bar\baz.  This bug is not reproducible in 1.2beta4.  -- mr@eng 8/7/1998
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.2fcs FIXED IN: 1.2fcs INTEGRATED IN: 1.2fcs
14-06-2004
EVALUATION This bug only occurs when resolving a path of the form X:foo, where X is the current drive. It does not occur when X is a drive other than the current drive. The fix is trivial. -- mr@eng 8/10/1998
10-08-1998