[ https://issues.apache.org/jira/browse/TIKA-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603300#comment-16603300 ]
Hudson commented on TIKA-2721: ------------------------------ UNSTABLE: Integrated in Jenkins build tika-2.x-windows #305 (See [https://builds.apache.org/job/tika-2.x-windows/305/]) TIKA-2721: removed spring-* from tika-parsers deps (grossws: rev b6c4f8e2617840075d546433f461b7df566e401a) * (edit) tika-parsers/pom.xml > Exclude Spring (transitive dependency) from tika-parsers > -------------------------------------------------------- > > Key: TIKA-2721 > URL: https://issues.apache.org/jira/browse/TIKA-2721 > Project: Tika > Issue Type: Bug > Components: packaging > Reporter: Konstantin Gribov > Assignee: Konstantin Gribov > Priority: Minor > Fix For: 2.0, 1.19 > > > {{uimafit-core}} brings {{spring-core}}, {{spring-beans}} and > {{spring-context}} with quite ancient version 3.2.x which is not required for > parsing and usually clash with actual Spring libs or just pollutes jar if > uberjar (shade plugin, onejar, assembly plugin with jar-with-dependencies > etc) is used. > Its exclusion from deps seems more or less safe to me. But formally it can be > seen as breaking change if someone depends on that tika-parsers provides > spring libs transitively. -- This message was sent by Atlassian JIRA (v7.6.3#76005)