tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Allison (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-2756) Switch to commons-lang 3
Date Mon, 11 Feb 2019 17:04:00 GMT

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

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

Although, wait, the scope of {{ctakes-core}} is {{provided}}.  If that's what we want, we
should make its excluded dependencies also provided.  IIRC, I excluded a number of dependencies
from {{ctakes-core}} and then added those dependencies with more modern versions to avoid
version conflicts.  So, I suspect this was my initial fault when I did that work to align
dependency versions, and we should be ok to make these {{provided}} as well.

> 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)

Mime
View raw message