[
https://issues.apache.org/jira/browse/OAK-10001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677321#comment-17677321
]
Julian Reschke commented on OAK-10001:
--------------------------------------
My suggestion is to bump up the Java version in Jackrabbit once we have to (I
assume that will be the case when we reference a new version of jackrabbit-api).
In that case, I would suggest to keep version numbers modest (as this is really
maintenance only).
That would mean:
- bump up Java version
- create new instable release
- branch 2.22 from trunk ("for Java 11 and newer")
Fortunately, we can EOL 2.16 this spring, so the number of branches will remain
manageable.
> Bump up minimal Java version to 11
> ----------------------------------
>
> Key: OAK-10001
> URL: https://issues.apache.org/jira/browse/OAK-10001
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: parent
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Major
> Fix For: 1.48.0
>
>
> Active support for Java 8 ended a few months ago (see
> [https://endoflife.date/java]).
> Java 11 has been available for four years, and offers various improvements
> (in particular, it contains extensions that may help in avoiding use of Guava
> (see OAK-7182)).
> (Note that even Java 11 will be out of active support in a few months - so a
> subsequent update to the next LTS release - Java 17 - is not that far away).
> Potential downsides:
> - backports to 1.22 might become harder (1.8 will be EOLd next spring
> anyway).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
