Hello @kurminkexam and thanks for taking the time to report your issue.
We’ve indeed noticed this remaining issue recently and fixed it in this pull request on Github https://github.com/algolia/algoliasearch-client-java-2/pull/709 which we plan to merge and release soon.
Once this will be released, you will then be able to download the new version (probably 3.11.0 or higher) to use the algoliasearch-apache-uber jAR as a working dependency (we’ve tested it in an actual AEM instance).
In the meantime, if this is blocking on your end, you can build the JAR yourself before the official release:
- Close the repository
- Checkout on the pull request branch
- Build the packages with
mvn clean package -DskipTests -Dmaven.javadoc.skip=true
- Use the generated uber JAR located under
The OSGi/AEM platforms are relatively new to us. Thank you for your patience and understanding while we do our best to make our Java library compliant with the OSGi bundling model.