That should not prevent us from moving. Tika 1.x is EOL for very long.
We need to make sure that our dependencies are clean and must not let us
block by other projects.
Worst case, we or the Oak team needs to provide a wrapper bundle for
Tika which fixes the imports.
Carsten
On 6/18/2026 6:57 PM, Eric Norman wrote:
I looked at those a while ago. And updating those to a recent tika looked
simple enough, but I found that deploying both the
tika-core:1.28.5/tika-parsers:1.28.5 (which are still required by OAK) and
the 3.x equivalent versions in the OSGi runtime at the same time did not
work due to the lack of proper version ranges in the Import-Package clause
of the manifest of the tika 1.x versions.
So for me, we are still blocked by OAK-9752
<https://issues.apache.org/jira/browse/OAK-9752> and pending the resolution
of that we should update the tika dependencies to the same version.
Regards,
Eric
On Thu, Jun 18, 2026 at 6:47 AM Carsten Ziegeler <[email protected]>
wrote:
We have (at least) two modules which currently require an unmaintained
version of Apache Tika (commons mime, commons contentdetection).
We have a year old issue for the starter where I added those two as well:
https://issues.apache.org/jira/browse/SLING-12047
Question is what are we going to do? Update to Tika 3.LATEST?
Regards
Carsten
--
Carsten Ziegeler
Adobe
[email protected]
--
Carsten Ziegeler
Adobe
[email protected]
