Adam

I cloned https://github.com/d-emrani/Sentry-Bug and ran `./gradlew assembleRelease` without error. The second report with incompatible versions is unrelated to the oss licenses plugin and should a new/separate issue.

So this is a bit of a weird one. With a clean Docker image with tools installed: ``` git clone https://github.com/d-emrani/Sentry-Bug.git cd Sentry-Bug ./gradlew assemble # Fails with stack overflow...

The oss-licenses-plugin tries to look at POM files for all transitive dependencies used by the app. If you use library A and library A uses library B (via POM dependency),...

I think this is resolved with #104

There is a [migration guide](https://developers.google.com/ml-kit/migration) which explains how to switch to the new MLKit version of these libraries. There is also an [issue with firebase-ml-vision 24.1.0](https://firebase.google.com/support/release-notes/android#mlkit-vision_v24-1-0), follow instructions on that...

It looks like sonatype.org no longer has a snapshot of the play-services-location library. What happens when you add google() to your build.gradle repositories section? https://developers.google.com/android/guides/setup#add_google_play_services_to_your_project That should resolve the official...

Another team works on this plugin and they're taking a look. If you could update with the latest changes from `master` that would help.

Alexander is correct. The Android Gradle Plugin only generates the dependency list that the plugin consumes for releasable builds.