[
https://issues.apache.org/jira/browse/TIKA-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18033842#comment-18033842
]
Tilman Hausherr commented on TIKA-4532:
---------------------------------------
Re 1, I agree that this can be replaced.
Re 2, I agree that the API from java itself should be used where possible.
About the rest: some is implemented in tika. However I'd rather argue for the
opposite, i.e. to have one central source of truth instead of copying code.
IIRC I replaced some a few weeks ago.
Re 3 and 4 no opinion, however tika-eval is used mostly by ourselves as a
quality tool, I'm not sure if that counts as "public API".
What I'm really wondering about, is that you're an apache member and are
arguing not to use an apache product. Is your argument part of something
bigger, e.g. to retire commons lang, or to split it in smaller entities?
> Drop commons-lang3 dependency
> -----------------------------
>
> Key: TIKA-4532
> URL: https://issues.apache.org/jira/browse/TIKA-4532
> Project: Tika
> Issue Type: Improvement
> Affects Versions: 3.2.3
> Reporter: Vladimir Sitnikov
> Priority: Major
>
> Currently, there are only a few commons-lang3 usages in apache tika (see
> https://github.com/search?q=repo%3Aapache%2Ftika%20commons.lang3&type=code ),
> and it would be great if
> commons-lang3 is a big dependency with lots of stuff, and it is unfortunate
> to get CVEs via commons-lang3:
> https://mvnrepository.com/artifact/org.apache.commons/commons-lang3
> See https://github.com/apache/maven-doxia/issues/1006
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
