A test with a tag `enablePreview false` should take precedence over libraries compiled with preview features enabled - analog to `enablePreview` and `enablePreview true`will always lead to compiling and runnging a test with preview features enabled.
Copied from the tag specification:
> If the tag is present but no argument given, a default value of true will be assumed.
> If the tag is not present, and a default value has been configured with an enablePreview entry in an enclosing TEST.properties file, then that default value will be used.
> If the tag is not present and no default value has been configured, a value of false will be assumed and no additional compile-time and run-time options will be provided.
That last sentence should be updated to include something like "— unless a library is used that requires such options."
Copied from the tag specification:
> If the tag is present but no argument given, a default value of true will be assumed.
> If the tag is not present, and a default value has been configured with an enablePreview entry in an enclosing TEST.properties file, then that default value will be used.
> If the tag is not present and no default value has been configured, a value of false will be assumed and no additional compile-time and run-time options will be provided.
That last sentence should be updated to include something like "— unless a library is used that requires such options."
- relates to
-
CODETOOLS-7903809 Invalid source release N with --enable-preview
- Resolved
- links to
-
Commit(master) openjdk/jtreg/b290244b
-
Review(master) openjdk/jtreg/225