-
Bug
-
Resolution: Fixed
-
P4
-
9, 10, 11, 12
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8216458 | 13 | Mark Reinhold | P4 | Resolved | Fixed | b03 |
| JDK-8217070 | 12.0.1 | Mark Reinhold | P4 | Resolved | Fixed | b03 |
| JDK-8270812 | 11.0.13-oracle | Abdul Kolarkunnu | P4 | Resolved | Fixed | b03 |
| JDK-8272420 | 11.0.13 | Aleksey Shipilev | P4 | Resolved | Fixed | b03 |
Two launcher tests, ExecutionEnvironment.java and Test7029048.java (in test/jdk/tools/launcher), still assume the old image layout in which a HotSpot shared library (libjava.so) is found in $JDK/lib/$ARCH/$VMTYPE on Linux and Solaris. The intermediate $ARCH directory was removed in JDK 9, as part of JEP 220 (Modular Run-Time Images) [1]. Since that time these tests have been succeeding anyway, because they don’t fail when the requested VM is not found.
The tests should be fixed to fail when the requested VM is not found, and to look for VM shared libraries in the proper location.
[1] http://openjdk.java.net/jeps/220
The tests should be fixed to fail when the requested VM is not found, and to look for VM shared libraries in the proper location.
[1] http://openjdk.java.net/jeps/220
- backported by
-
JDK-8216458 Some launcher tests assume a pre-JDK 9 run-time image layout
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- blocks
-
JDK-8210670 Accept double-dash VM-name options at launch time
-
- Open
-
- relates to
-
-
- Resolved
-
(1 relates to, 2 links to)