[
https://issues.apache.org/jira/browse/LANG-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429800#comment-16429800
]
Gary Gregory commented on LANG-1389:
------------------------------------
Since Oracle or any JRE vendor can change this string with any release, and
even the version numbering scheme, I do not see how we can do better than test
and update if necessary for each JRE release.
IMO, we have to maintain our class and reference the Java 9 class as a better
alternative.
When Lang 4.0 comes out we can break BC and remove it completely if we require
Java 9 by then.
At work, we are in the middle of moving Java 7 to 8. Forget Java 9, 10 and 11
EAs... Sure we test with newer JREs but these are not our baseline. I suspect
most people with large code bases will be way behind in Java releases,
especially with Oracle's new release cadence.
> Deprecate JavaVersion in favor of java.lang.Runtime.Version
> -----------------------------------------------------------
>
> Key: LANG-1389
> URL: https://issues.apache.org/jira/browse/LANG-1389
> Project: Commons Lang
> Issue Type: Task
> Components: lang.*
> Affects Versions: 3.7
> Reporter: Michael Osipov
> Priority: Major
>
> With the rapid release cycle of Java {{JavaVersion}} does not really work
> anymore. We at Maven have constant issues with our subprojects for missing
> Java version in {{JavaVersion}} enum. To solve this problem, Commons Lang
> must be release at least every six months and we have re-release all affected
> components. Since this does not scale, I would recommend to deprecate this
> enum in favor of {{java.lang.Runtime.Version}} or have a better non-enum
> approach to it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
