[
https://issues.apache.org/jira/browse/TIKA-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-5069:
------------------------------
Description:
For 3.4.0, we have to bump tika-server to jdk17. We had done a half measure
that still kind of allowed jdk11 to build parts of the repo.
If we're requiring jdk17 in one module, I think we should blanket require it
for the full build. We should still target jdk11 for tika-core, tika-app etc.
tbh, I thought we did this earlier when we bumped tika-server in 3.x to jdk17.
was:
For 3.4.0, we have to bump tika-server to jdk17. We had done a half measure
that still kind of allowed jdk11 to build parts of the repo.
If we're requiring jdk17 in one module, I think we should blanket require it
for the full build. We should still target jdk11 for tika-core, tika-app etc.
> Require jdk17 for the full build of 3.x
> ---------------------------------------
>
> Key: TIKA-5069
> URL: https://issues.apache.org/jira/browse/TIKA-5069
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
>
> For 3.4.0, we have to bump tika-server to jdk17. We had done a half measure
> that still kind of allowed jdk11 to build parts of the repo.
> If we're requiring jdk17 in one module, I think we should blanket require it
> for the full build. We should still target jdk11 for tika-core, tika-app etc.
> tbh, I thought we did this earlier when we bumped tika-server in 3.x to jdk17.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)