[
https://issues.apache.org/jira/browse/TIKA-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136914#comment-18136914
]
Hudson commented on TIKA-5021:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk17 #1770 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1770/])
TIKA-5021 fail on bytecode > 17 (#3510) (github:
[https://github.com/apache/tika/commit/29eea74873fac9535c4bbd24cc27e264f7d509ba])
* (edit) tika-parent/pom.xml
> Add byte code check in 3.x and 4.x
> ----------------------------------
>
> Key: TIKA-5021
> URL: https://issues.apache.org/jira/browse/TIKA-5021
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Major
>
> In 3.x, we made the decision to require Java 17 for tika-server. The problem
> is that we've been building 3.x with Java 17 and higher and a few
> dependencies build just fine with 17, but will fail at runtime with Java 11.
> I recently had no problem upgrading to POI 6 in 3.x, and then running it on
> Java 17, but that fails with Java 11.
> We should add a strict byte code check in 3.x and 4.x to ensure that
> dependencies really are at or below the targeted versions.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
