[
https://issues.apache.org/jira/browse/TIKA-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182077#comment-17182077
]
Kenneth William Krugler commented on TIKA-3183:
-----------------------------------------------
Apologies in advance if this has already been hashed out :(
I haven't been following all the details of where Tika is at with dependency
management, but based on my experience with Flink, I think we'd want to shade
anything that's a Tika direct dependency, to avoid version hell with all of the
parser/other modules transitive dependencies.
Though that doesn't address the issue of two modules depending on different
versions of the same jar. Or are we relying on classloader helicopter stunts to
avoid that?
> Tika 2.0.0 -- Move all versions to properties in tika-parent
> ------------------------------------------------------------
>
> Key: TIKA-3183
> URL: https://issues.apache.org/jira/browse/TIKA-3183
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Trivial
> Labels: 2.0.0
>
> I've been following the principle of property-ifying versions at the lowest
> branch pom.xml that covers the modules for that dependency. Now that we have
> more hierarchy, maintenance would be easier if we centralized versions in
> tika-parent.
> Any objections?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
