P4
This is for discussion.
To support some testing scenarios, jtreg currently can use two JDKs ... the "compileJDK", used to compile tests, and the "testJDK", used to execute tests.
There are times, such as @run driver, when it would be good to execute code on the compile JDK.
One way of generalizing the existing concepts would be have a "stable JDK" which is typically used for compilation, and a "test JDK" which is used for executing test code. The action tags that require a JDK could support options /stable, /test, which could be used to override the "default" assignment.
In particular, this would allow "@run driver" to be able to use the stable JDK. It is a separate but secondary decision whether that should be a new default or not.
To support some testing scenarios, jtreg currently can use two JDKs ... the "compileJDK", used to compile tests, and the "testJDK", used to execute tests.
There are times, such as @run driver, when it would be good to execute code on the compile JDK.
One way of generalizing the existing concepts would be have a "stable JDK" which is typically used for compilation, and a "test JDK" which is used for executing test code. The action tags that require a JDK could support options /stable, /test, which could be used to override the "default" assignment.
In particular, this would allow "@run driver" to be able to use the stable JDK. It is a separate but secondary decision whether that should be a new default or not.