[
https://issues.apache.org/jira/browse/TIKA-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630029#comment-17630029
]
Tim Allison commented on TIKA-3735:
-----------------------------------
This kinda feels like we're hitting a tipping point. Should we keep the 2.6.x
branch for Java 8 (and bugfixes) and start on Java 11 for 2.7.x? Or do we need
wait for Tika 3.x before requiring Java 11... Or do we just sit on our hands
for a few more months/year...?
> Require Java 11 for 2.x at some point
> -------------------------------------
>
> Key: TIKA-3735
> URL: https://issues.apache.org/jira/browse/TIKA-3735
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
>
> This follows on from discussion we had on the user/dev list for when we want
> to require Java 11. I think the consensus was: wait until we have to.
> The following libraries require > Java 8 at the moment. I don't think
> updating any of these is critical, but I do want to document where we're
> stuck.
> We can modify/edit this list as necessary:
> * Apache OpenNLP 2.0.0 requires Java 11.
> * DL4J 1.0.0-M2.1 - datavec-data-image-1.0.0-M2.1.jar requires Java 11
> * Lucene 9.x -- used in tika-eval
> * icu4j -- we can't upgrade past 62.2 (April 2019) because that is the latest
> version that is compatible with Lucene 8.11.1
> (https://github.com/apache/tika/pull/587)
> * mime4j -- the last 2 (or three?) releases have been accidentally built with
> Java 9 without the correct release=8. This should be fixed in the next
> release.
> * Fakeload
> *
> [checkstyle|https://mail.google.com/mail/u/0/#label/lists%2Ftika/WhctKKXXHvjnJRRdBSwLbKkDkXQtRnWGDhblVMQQZhjsDGrFpRMRQJJrZSdskrNCqcmTtjL]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
