-
Bug
-
Resolution: Fixed
-
P3
-
7
-
b74
-
generic
-
generic
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2194730 | OpenJDK6 | Jonathan Gibbons | P4 | Resolved | Fixed | b21 |
From Peter Ahe:
The problem [with FileObject#getName()] is that when I added getName, it was accidentally
implemented by a deprecated method in BaseFileObject. This method
returns the base name, for example, "Object.class" rather than
"/usr/java/jdk/lib/ct.sym(META-INF/sym/rt.jar/java/lang/Object.class)".
The intent was that this method would return a name which tells the
user something, but does not use an absolute path if the user didn't.
The problem [with FileObject#getName()] is that when I added getName, it was accidentally
implemented by a deprecated method in BaseFileObject. This method
returns the base name, for example, "Object.class" rather than
"/usr/java/jdk/lib/ct.sym(META-INF/sym/rt.jar/java/lang/Object.class)".
The intent was that this method would return a name which tells the
user something, but does not use an absolute path if the user didn't.
- backported by
-
JDK-2194730 JavaFileObject getName issues
-
- Resolved
-
- relates to
-
-
- Closed
-
-
-
- Closed
-