[TIKA-3934] Reogranize POMs parent chain to avoid leaking dependency management downstream

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.6.0
• Fix Version/s: 2.7.0
• Component/s: depedency
• Assignee: Konstantin Gribov
• Reporter: Konstantin Gribov
• Created: 19/Nov/22 20:22
• Updated: 06/Feb/23 16:32

Description

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:

• make tika reactor depend on tika-parent and all other tika-* modules on the reactor
• move all our dependency management and build related configuration to the reactor (tika root project)

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