-
Sub-task
-
Resolution: Other
-
P4
-
None
-
None
-
None
There are tests that rely on specific JAR file names being present at run-time, which they don't control, which 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's an initial list of tests known to rely on specific JAR file names:
- https://github.com/openjdk/jdk/blob/master/test/jdk/tools/jpackage/junit/junit.java
- https://github.com/openjdk/jdk/blob/master/test/hotspot/jtreg/runtime/cds/appcds/dynamicArchive/CDSStreamTestDriver.java
- 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's an initial list of tests known to rely on specific JAR file names:
- https://github.com/openjdk/jdk/blob/master/test/jdk/tools/jpackage/junit/junit.java
- https://github.com/openjdk/jdk/blob/master/test/hotspot/jtreg/runtime/cds/appcds/dynamicArchive/CDSStreamTestDriver.java