Migrate to Apache Tika 4.0.0 - #6754
Merged
Merged
Conversation
Bump tika-core to 4.0.0 and drop the no-op tika-parsers aggregator (packaging=pom, non-transitive: it shipped no jar and only pulled extra BOMs into dependency verification). Replace the removed TikaConfig with a plain Tika() for MIME detection in HTTPFileArg and ParseCurlCommandAction, and delete the now-unused tika-config.xml. Wrap the Parser.parse input in TikaInputStream in Document, as the Parser interface now requires it in 4.x. Add trusted keys for the BOMs imported by tika-core's parent POM (com.azure, io.grpc, org.eclipse.jetty, org.testcontainers) and update the expected release jar entry to tika-core-4.0.0.jar. Reflect the bump in the 6.0.0 "Non-functional changes" changelog entry (the dev cycle already moved 1.x -> 3.x; update it to 4.x). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates Apache Tika from 3.2.3 to the newly released 4.0.0 GA.
tika-coreto 4.0.0 inbom-thirdparty.tika-parsersaggregator: it ispackaging=pomand declarednon-transitive, so it shipped no jar — it only dragged extra BOMs
(grpc/azure/jetty/testcontainers) into dependency verification. JMeter
bundles only
tika-core; document parsing still relies on auser-supplied
tika-app.jarat runtime.API changes handled
TikaConfigwas removed in 4.x. InHTTPFileArgandParseCurlCommandActionit was only used to setinitializableProblemHandler="ignore", which is off the MIME-detectionpath (
tika.detectuses detectors, not parsers). Replaced with a plainnew Tika()and deleted the now-unusedtika-config.xml.Parser.parsenow requires aTikaInputStream.Documentnow wrapsits byte array with
TikaInputStream.get(...). Body text extraction isunchanged (
BodyContentHandlerstill emits plain text by default).Build / infrastructure
tika-core's parent POM(
com.azure,io.grpc,org.eclipse.jetty,org.testcontainers) ingradle/verification-metadata.xml. No jars from these are pulled — onlytheir
.pomsignatures are validated.tika-core-4.0.0.jar.Testing
./gradlew :src:core:classes :src:protocol:http:classes style— pass.:src:protocol:http:testforTestHTTPFileArg,TestHTTPFileArgs,ParseCurlCommandActionTest— 30 passed, 0 failed.:src:dist:verifyReleaseDependencies— runtime classpath matches theexpected jar list; signatures validated across the full runtime graph.
Note (out of scope)
Document.javastill keys its "missing tika" hint offjava.class.path contains "tika-app". In 4.xtika-appships as a zipdistribution rather than a fat jar, so that heuristic is now stale — left
untouched here as it concerns user runtime setup, not this build.
🤖 Generated with Claude Code