[ https://issues.apache.org/jira/browse/TIKA-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15162978#comment-15162978 ]
John Patrick commented on TIKA-1868: ------------------------------------ I've created a pull requests so you can see what I proposed, I accept it might be rejected. https://github.com/apache/tika/pull/76 > create clean tika-server jar and shaded classifier jar > ------------------------------------------------------ > > Key: TIKA-1868 > URL: https://issues.apache.org/jira/browse/TIKA-1868 > Project: Tika > Issue Type: Bug > Components: server > Affects Versions: 1.11, 1.12 > Environment: n/a > Reporter: John Patrick > Labels: github-import, maven, newbie, patch > Fix For: 1.13 > > > If using tika-server-VERSION.jar as a standalone component it works. But if > you use it as a dependency so is included with other jars then it causes > classpath issues specifically around jackson. > The project I'm working on is using Jackson 2.6.1, we have just added tika > but when adding tika-server-VERSION.jar we have discovered it contains > Jackson 2.4.0 classes. > I've update the maven build so two jar's are now created. > 1) tika-server-VERSION.jar correct clean jar > 2) tika-server-VERSION-standalone.jar what was previously created > This in my view is more inline with how maven should be being used to create > jars as the previous way restricted the consumers ability to override maven > dependencies. > I've also updated the documentation in source control that refs to > tika-server to include the new tika-server standalone jar. I realize other > documentation might also need to change. -- This message was sent by Atlassian JIRA (v6.3.4#6332)