It would be convenient to support the use of ${property.name} in the arguments for an action (@compile, @run main, etc).
The sat of property names should be the same as used in @requires.
One primary use case is to specify the current JDK version in @compile tests that use preview features: for example
@compile --source ${jdk.version} --enable-preview Test.java
There are potential additional use cases in test/hotspot/jtreg, which currently uses a library class PropertyResolvingWrapper, which sets a precedent for multiple names within a single argument, such as `${os.family},${os.version}`
For compatibility, it could either be an opt-in feature, using TEST.ROOT/TEST.properties (i.e. default is off), or an opt-out mechanism, where the default is off when the requiredVersion is <=b13, on for requiredVersion is >= b14
The sat of property names should be the same as used in @requires.
One primary use case is to specify the current JDK version in @compile tests that use preview features: for example
@compile --source ${jdk.version} --enable-preview Test.java
There are potential additional use cases in test/hotspot/jtreg, which currently uses a library class PropertyResolvingWrapper, which sets a precedent for multiple names within a single argument, such as `${os.family},${os.version}`
For compatibility, it could either be an opt-in feature, using TEST.ROOT/TEST.properties (i.e. default is off), or an opt-out mechanism, where the default is off when the requiredVersion is <=b13, on for requiredVersion is >= b14
- relates to
-
JDK-8219408 Tests should handle ${} in the view of jtreg "smart action"
- Open
-
JDK-8219254 Update explicit uses of latest source/target in langtools tests to a property
- Resolved
-
JDK-8219140 get rid of vmTestbase/PropertyResolvingWrapper
- Closed