P2
jtreg needs to support the new "long form" JDK options, as defined in JEP 293 and JEP 261.
Specifically, this includes:
- Recognizing and handling long-form options that use white-space to separate their argument. This applies to options on the command line, and also options in actions within test descriptions (e.g. @compile, @run main, etc)
- Updating support certain Jigsaw options on the jtreg command line, such as -addmods, -limitmods, -Xpatch
- Updating the command lines generated by jtreg to invoke java and javac
- Updating the code to generate the "module configuration summary", which is done, in part, by analysing command lines
----
As in a similar occasion in recent past, jtreg should allow a "transition period" where both the old and new JDK options will be accepted, and one set or the other will be generated, based on a temporary property "useNewOptions=true" in the TEST.ROOT file.
Specifically, this includes:
- Recognizing and handling long-form options that use white-space to separate their argument. This applies to options on the command line, and also options in actions within test descriptions (e.g. @compile, @run main, etc)
- Updating support certain Jigsaw options on the jtreg command line, such as -addmods, -limitmods, -Xpatch
- Updating the command lines generated by jtreg to invoke java and javac
- Updating the code to generate the "module configuration summary", which is done, in part, by analysing command lines
----
As in a similar occasion in recent past, jtreg should allow a "transition period" where both the old and new JDK options will be accepted, and one set or the other will be generated, based on a temporary property "useNewOptions=true" in the TEST.ROOT file.