A quick question about these.   How are we describing the intended usage
for these new releases?  From what I can tell the "commons
contentdetection" one isn't deployed in the starter project, but the
"commons mime" one is.  The new "commons mime" release currently only
resolves in the starter project because the tika dependencies (for the 4.x
dependency) are marked as optional.  And if I recall correctly, it is
currently impossible to have both the tika 1.x and 4.x artifacts in the
same deployment due to some import-package instructions in the 1.x
artifacts without proper version ranges that cause a conflict.  So any code
that uses those "tika" code paths from "commons mime" would not work
anymore if people update to these and keep tika 1.x in the project
distribution?

So, I'm suggesting that these may not be ready to be used until oak-lucene
updates to tika 4.x as well.

Regards,
Eric

On Thu, Nov 12, 2026 at 1:05 AM Carsten Ziegeler via dev <
[email protected]> wrote:

> Hi,
>
> We solved 2 issues in Commons Mime:
>
> https://issues.apache.org/jira/projects/SLING/versions/12356847
>
> and 5 issues in Commons Contentdetection:
>
> https://issues.apache.org/jira/projects/SLING/versions/12347767
>
> Staging repository:
>
> https://repository.apache.org/content/repositories/orgapachesling-3138/
>
> You can use this UNIX script to download the release and verify the
> signatures:
>
>
> https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 3138 /tmp/sling-staging
>
> Please vote to approve this release:
>
>    [ ] +1 Approve the release
>    [ ]  0 Don't care
>    [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> Regards
> Carsten
> --
> Carsten Ziegeler
> Adobe
> [email protected]
>
>

Reply via email to