Bump tika-core from 3.3.0 to 3.3.2 - #1891
Closed
IvanBorislavovDimitrov wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
Superseded by #1892, which is opened from a branch in this repository so the CI checks (including the Sonar scan) run with the required credentials. |
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.
What
Upgrades
org.apache.tika:tika-corefrom3.3.0to3.3.2(patch release).The version is managed via the
tika-core.versionproperty in the parent POM and consumed bymultiapps-controller-core.Why
Routine dependency maintenance — moving to the latest available patch release of Apache Tika.
Verification
mvn dependency:tree -pl multiapps-controller-core -Dincludes=org.apache.tika:tika-coreresolvestika-core:3.3.2:compile.mvn clean test-compile -pl multiapps-controller-core --also-make— BUILD SUCCESS; no source changes required (patch-level upgrade, no API changes).