[
https://issues.apache.org/jira/browse/TIKA-3183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182085#comment-17182085
]
Tim Allison commented on TIKA-3183:
-----------------------------------
AFAIK, we've mercifully been able to get by without conflicts with some
patience. We're using maven's enforcer DependencyConvergence to identify
conflicts.
We'll have an upcoming issue with POI, when that goes to 4.x and jackcess will
likely be on 3.x for a bit...so maybe shade then?
Or, if you think we should do a more general shading, 2x is now main...have at
it! :D
This issue was more to do with the housekeeping of where to write the versions
for easy modifications.
> 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)
