Reminder: avoid hard-coding release values in regression tests (original) (raw)
joe darcy joe.darcy at oracle.com
Fri Jun 22 17:03:57 UTC 2018
- Previous message: JDK 11 enters Rampdown Phase One next week
- Next message: JDK-8161256
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello,
With the JDK 11 and JDK 12 split coming soon [1], work has begun on preparing the JDK 12 b01 changes to increment the version number, add 12 as an option to javac's -source and -target options, etc.
This effort has revealed a number of regression tests which hard-code release values in various ways.
Please avoid this technique except when strictly necessary as it increases the maintenance cost of starting a new JDK release. Prefer to query the current release programmatically and dynamically construct earlier and later release values as needed.
Cheers,
-Joe
[1] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-June/001462.html
- Previous message: JDK 11 enters Rampdown Phase One next week
- Next message: JDK-8161256
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]