-
Enhancement
-
Resolution: Fixed
-
P3
-
11.0.15-oracle, 17.0.3-oracle, 18.0.1, 19
-
b04
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8280043 | 18.0.1 | Erik Joelsson | P3 | Resolved | Fixed | b04 |
| JDK-8280038 | 17.0.3-oracle | Dukebot | P3 | Resolved | Fixed | b03 |
| JDK-8280037 | 11.0.15-oracle | Erik Joelsson | P3 | Resolved | Fixed | b03 |
| JDK-8281589 | 11.0.14.0.2-oracle | Evan Whelan | P3 | Resolved | Fixed | b01 |
This will reduce the timing and complexity needed when starting new JDK releases. We are already defining the version numbers used in the build in make/conf/version-numbers.conf, so we already know this isn't causing merge issues. Updating this file as well will not add much to the new release change.
Once done in mainline, I would like to also backport this to all active update releases maintained by Oracle. (Other OpenJDK update projects have already adopted this practice.)
- backported by
-
JDK-8280037 Define version in .jcheck/conf
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- blocks
-
SKARA-1299 Remove fixVersion config for mainline jdk
-
- Resolved
-
- relates to
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk18u/338d3d2d
-
Commit
openjdk/jdk/6b906bba
-
Review
openjdk/jdk18u/5
-
Review
openjdk/jdk/6929