JDK-4070044 : java.io.File.getCanonicalPath does not handle drive-relative paths (win32)
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.io
  • Affected Version: 1.1.3,1.2.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_2.5.1,windows_95
  • CPU: x86,sparc
  • Submitted: 1997-08-06
  • 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.2beta4Fixed
Related Reports
Duplicate :  
JDK-4071312 - java.io.File: Problem accessing files in root directory
Relates :  
JDK-4207599 - (1.1) java.io.File does not handle drive-relative paths (win32)
Relates :  
JDK-4164823 - java.io.File.getCanonicalPath still does not handle drive-relative paths (win32)
Relates :  
JDK-4131169 - java.io.File: Respecify using abstract pathnames rather than strings
Description
Under windows, something like:

    C:foo 

Is the same as:

    C:\current\directory\foo

At least that has always been my understanding (i.e., cd to cd:\foo, create
bar.txt, and type:  "type c:bar.txt". 

getCanonicalPath when passed "C:" or "C:foo" seems to be returning
C:\current\directory\c: or C:\current\directory\c:foo.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: 1.2beta4 INTEGRATED IN: 1.2beta4
14-06-2004
EVALUATION Fixed, as part of the rewrite for 4131169. -- mr@eng 5/14/1998
14-05-1998
SUGGESTED FIX See the suggested fix for 4071583. robert.wilson@Eng 1998-01-21
21-01-1998