The approach suggested by @onichols-pivotal is well-intentioned, but could
vastly increase the scope of the work. Briefly:
- Java version numbers appear in two contexts: As system requirements and as
strings in examples.
- Use of Java versions in system requirements prompted the current two-part
division of the variables into main-version and minimum-update. There are only
a few occurrences of these, but the variables ensure that they roll in sync
with new releases.
- Java versions in examples are scattered throughout the User Guide. This PR
addresses 10 of these, but there are almost certainly more. In addition, you
can see from the diffs that there are adjacent lines containing hard-coded Java
info ("Java version: 1.0.0 user1 041216 2016-11-12 11:18:37 -0700") that are
likely out-of-date. Identifying and variable-izing all such occurrences is way
beyond the scope of this JIRA ticket.
My recommendation is to accept @alb3rtobr 's current solution as a good step in
the right direction.
[ Full content available at: https://github.com/apache/geode/pull/4142 ]
This message was relayed via gitbox.apache.org for
[email protected]
