[
https://issues.apache.org/jira/browse/TIKA-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17875574#comment-17875574
]
Tim Allison commented on TIKA-4280:
-----------------------------------
bq. Before releasing the real 3.0.0 we need to remove any "-M" dependencies
I see commons.collections4 4.5.0-M2 and dl4j 1.0.0-M2.1 in Tika's parent pom.
For commons collections4, the last non-M release was in 2019. Is there enough
of a reason to revert to 4.4?
For dl4j, the last non-M release would take us back to 2017 with 0.9.1. Is
there enough of a reason to revert to 0.9.1?
Looking at transitive dependencies, I see
org.datavec:datavec-data-image:jar:1.0.0-M2.1, org.nd4j:jackson:jar:1.0.0-M2.1
and a few other org.nd4j:* (which are consistent with dl4j). So no surprises in
transitive dependencies?
Are there others *-M dependencies? Or, has this already been cleaned up? Thank
you [~tilman] for raising this point.
> Tasks for the 3.0.0 release
> ---------------------------
>
> Key: TIKA-4280
> URL: https://issues.apache.org/jira/browse/TIKA-4280
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
>
> I'm too lazy to open separate tickets. Please do so if desired.
> Some items:
> * Before releasing the real 3.0.0 we need to remove any "-M" dependencies
> * Decide about the ffmpeg issue and the hdf5 issue
> * Run the regression tests vs 2.9.x
> * Convert tika-grpc to use the dependency plugin instead of the shade plugin
> * Turn javadocs back on. I got errors during the deploy process because
> javadoc needed the auto-generated code ("cannot find symbol
> DeleteFetcherRequest"). We need to enable javadocs for the rest of the
> project.
> * TIKA-4290 Tilman question
> Other things? Thank you [~tilman] for the first two!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
