P3
It would be convenient for a family of tests to use externally provided jar files.
One such possibility would be to allow such jar files to be bundled with jtreg, in the jtreg/lib directory, and to extend the meaning of
@library foo.jar
to be able to refer to such libraries, such that they will be included on the compile and runtime classpath.
Currently, @library foo.jar can be used to refer to a library that has been checked in to the test source directory.
Option 1: if foo.jar is not found in the directory of the defining file, check in the lib directory
Option 2: use some other syntax to indicate the jar file is to be found in the lib directory
Option 3: look up the location of the file in TEST.ROOT
One such possibility would be to allow such jar files to be bundled with jtreg, in the jtreg/lib directory, and to extend the meaning of
@library foo.jar
to be able to refer to such libraries, such that they will be included on the compile and runtime classpath.
Currently, @library foo.jar can be used to refer to a library that has been checked in to the test source directory.
Option 1: if foo.jar is not found in the directory of the defining file, check in the lib directory
Option 2: use some other syntax to indicate the jar file is to be found in the lib directory
Option 3: look up the location of the file in TEST.ROOT
- duplicates
-
CODETOOLS-7901576 Support referencing jar files from JDK and JTREG
-
- Closed
-