Konstantin Gribov created TIKA-3934:
---------------------------------------
Summary: Reogranize POMs parent chain to avoid leaking dependency
management downstream
Key: TIKA-3934
URL: https://issues.apache.org/jira/browse/TIKA-3934
Project: Tika
Issue Type: Improvement
Components: depedency
Affects Versions: 2.6.0
Reporter: Konstantin Gribov
Assignee: Konstantin Gribov
Fix For: 2.7.0
Tika's BOM (Bill of Materials) artifact has {{tika-parent}} as a parent POM and
thus forces a lot of dependency versions on downstream users.
For example if one use only PDF module there's no reason to force
Netty/Jetty/CXF/whatever versions.
I propose the following:
* move all our dependency management and build related configuration to the
reactor ({{tika}} root project)
* make {{tika}} rector depend on {{tika-parent}} and all other {{tika-*}}
modules on the reactor
I've started these work last week and will publish first PR for review soon.
Moving parts from {{tika-parent}} to {{tika}} may take some time so little
steps without build disruption is a must
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
