Hello @bramakrishnan and thank you for the detailed error,
AEM environment is relatively new to us but we would be happy to better integrate our Java library with it. The pull request which my colleague @antoine.hemery mentioned is the first step in that direction: it makes sure that our Apache Uber JAR, which you can find here, is a valid OSGi bundle that you can import in an AEM application.
Your issue does not seem to be related to the build itself but to the dependency fetching. I can see two potential issues here:
either your application is not able to load libraries from the Maven Central repository, in that case, I’d recommend you to ensure it’s correctly configured (we are interested if you make any progress here, since we don’t have an AEM environment at hand)
or your application correctly fetch our Algolia dependency but is not considered a valid OSGI bundle (the pull request I’ve shared with you is not yet released, it will be in the next coming days in an upcoming 3.10.0 version)
I’m really interested to hear from you regarding my first point. Feel free to send us links that we could follow to learn more about dependency fetching in AEM.