-
Bug
-
Resolution: Fixed
-
P4
-
19
-
b22
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8292248 | 17.0.6-oracle | Harold Seigel | P4 | Resolved | Fixed | b01 |
| JDK-8294344 | 17.0.6 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
Tests generated by CDSMHTest_generate.sh scripts include a hard-coded assumption on from where JUnit classes are loaded from. Namely: junit.jar This filename will change in JTREg 7 as described in https://bugs.openjdk.java.net/browse/CODETOOLS-7903047 and attached PRs.
In addition, the code seems to fail on splitting the class path correctly on Windows systems using Cygwin.
Possible fix for both issues: Use the location information stored in JUnit Test class' runtime representation.
String junitJar = Path.of(Test.class.getProtectionDomain().getCodeSource().getLocation().toURI()).toString();
In addition, the code seems to fail on splitting the class path correctly on Windows systems using Cygwin.
Possible fix for both issues: Use the location information stored in JUnit Test class' runtime representation.
String junitJar = Path.of(Test.class.getProtectionDomain().getCodeSource().getLocation().toURI()).toString();
- backported by
-
JDK-8292248 Remove dependence on JAR filename in CDS tests
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
-
-
- Closed
-
- links to
-
Commit
openjdk/jdk17u-dev/3b48de56
-
Commit
openjdk/jdk/52dbfa99
-
Review
openjdk/jdk17u-dev/716
-
Review
openjdk/jdk/8624
(3 links to)