JDK-6759796 : test/tools/javac/6348193/T6348193.java fails if there are empty entries on the bootclasspath
- Type: Bug
- Component: tools
- Sub-Component: javac
- Affected Version: 7
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2008-10-15
- Updated: 2011-05-18
- Resolved: 2011-05-18
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.
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.
| JDK 7 | Other |
|---|---|
7 b39Fixed  |
OpenJDK6Fixed |
Description
The Java syystem (boot) classloader is inconsistent w.r.t. empty entries on the bootclasspath. They are ignored for the purposes of loading classes, but not ignored when locating resources. The latter behavior affects this test which uses getResource() to locate a class file. In the specific circumstances of this test (which is in the unnamed package, per usual), the empty path element can cause getResource to return an unexpected result.
The fix/workaround is to use System.getProperties("test.classes") instead of getResource().
Comments
|