-
Sub-task
-
Resolution: Fixed
-
P4
-
17, 18, 19, 20
-
b12
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8314648 | 17.0.10-oracle | Ludvig Janiuk | P4 | Resolved | Fixed | b01 |
JDK-8310289 | 17.0.9 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
There are tests that rely on specific JAR file names being present at run-time, which they don't control, as they are normally provided by jtreg's binary image. Examples for such JAR files names are:
- junit.jar
- hamcrest.jar
- testng.jar
These tests expect those specific JAR files being present in:
- jtreg's lib directory
- the value returned by System.getProperty("java.class.path")
Here is one such test in question:
https://github.com/openjdk/jdk/blob/master/test/jdk/tools/jpackage/junit/junit.java
There may be more under "test/jdk/tools/jpackage"
- junit.jar
- hamcrest.jar
- testng.jar
These tests expect those specific JAR files being present in:
- jtreg's lib directory
- the value returned by System.getProperty("java.class.path")
Here is one such test in question:
https://github.com/openjdk/jdk/blob/master/test/jdk/tools/jpackage/junit/junit.java
There may be more under "test/jdk/tools/jpackage"
- backported by
-
JDK-8310289 Tests should not rely on specific JAR file names (jpackage)
- Resolved
-
JDK-8314648 Tests should not rely on specific JAR file names (jpackage)
- Resolved
- blocks
-
JDK-8289798 Update to use jtreg 7
- Resolved
- relates to
-
JDK-8316547 Use JUnit.dir jtreg property with jpackage JUnit tests
- Resolved
- links to
-
Commit openjdk/jdk17u-dev/f21f9a44
-
Commit openjdk/jdk/45c3e898
-
Review openjdk/jdk17u-dev/1460
-
Review openjdk/jdk/9944
(3 links to)