[jira] [Commented] (TIKA-2756) Switch to commons-lang 3

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (TIKA-2756) Switch to commons-lang 3

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/TIKA-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765152#comment-16765152 ]

Tim Allison commented on TIKA-2756:
-----------------------------------

Ugh.  I'm still seeing a dependency on commons-lang in {{uima}} which we rely on extensively in our CTAKES parser:

{noformat}
 +- org.apache.uima:uimafit-core:jar:2.4.0:compile
[INFO] |  \- commons-lang:commons-lang:jar:2.6:compile
{noformat}

As [~grossws] noted above, though, I'm not sure this will cause problems?  We were getting a clean Java 11 build even before the upgrade to jackcess 3.0.0.  I'll kick the tires on my end.  Please kick the tires on yours.

> Switch to commons-lang 3
> ------------------------
>
>                 Key: TIKA-2756
>                 URL: https://issues.apache.org/jira/browse/TIKA-2756
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Robert Munteanu
>            Priority: Major
>
> Tika 1.9.1 is using the legacy commons-lang 2.x series. This series is not going to receive updates anymore and is completely superseded by commons-lang 3.x .
> Projects that use Tika are blocked from dropping commons-lang 2.x due to this dependency.
> The link that I found was from tika-parsers to jackcess and then to commons-lang 2.6
> {noformat}
> [INFO] +- com.healthmarketscience.jackcess:jackcess:jar:2.1.12:compile
> [INFO] |  \- commons-lang:commons-lang:jar:2.6:compile
> {noformat}
> If I understand correctly, this is the only commons-lang 2.x dependency from the Tika runtime and it would be great to remove it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)