[ANY23-552] Change scope of Tika dependency to provided

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.6
• Fix Version/s: 2.8
• Component/s: build, dependency
• Assignee: Lewis John McGibbney
• Reporter: Lewis John McGibbney
• Created: 02/Jan/22 23:48
• Updated: 21/Feb/22 18:24

Description

Right now Any23 defines the dependency on tika-core and tika-parsers-standard-package without scope meaning that a default scope of compile is therefore assumed. In some cases this can be very inconvenient as the transitive version of Tika (and subsequent Tika dependencies) may introduce unwanted and unnecessary issues in the application dependency management logic.
I am proposing that we change the scope of the Tika dependencies to <provided> meaning that we expect the application JDK or container to provide the Tika dependencies at runtime. This also provides flexibility for the application as now they can specify exactly which version of Tika they wish to rely on and use for mimetype detection and encoding.
I also propose that we make the MIMETypeDetector implementation configurable which it is currently not. For example, it could easily be added to default-configuration.properties.