Failed to resolve deps for com.google.firebase:firebase-analytics:aar:21.5.0 about rules_jvm_external HOT 4 CLOSED

I believe this is the same issue as #909 but with a different artifact.

from rules_jvm_external.

The key to troubleshoot this is to enable verbose mode in jvm_rules_external, obtain coursier args, replay coursier command with 'resolve' action and --tree param.

Example : /Library/Java/JavaVirtualMachines/temurin-11.jdk/Contents/Home/bin/java -noverify -jar /private/var/tmp/_bazel_oliviern/dd52b20a76c39eca281d5f4cd222340b/external/maven/coursier resolve "com.google.firebase:firebase-analytics:21.5.0,type=aar" --verbose --no-default --checksum SHA-1,MD5 --repository https://maven.google.com --repository https://repo1.maven.org/maven2 --cache v1 --tree

Conclusion : starting with version > 20.4.0, com.google.firebase:firebase-common-ktx is wrongly published and specify a jar dependency that doesn't exist (firebase-component).

Fix : file github issue to Google to fix their POM in future versions + consider implementing the same behavior as Gradle (which resolves the jar/aar conflict differently - maybe by implementing fallback when jar can't be found?)

Temp : pin version 20.4.0 (i.e explicitly add coord to WORKSPACE so that it takes precedences on 20.4.1 or 20.4.2).

from rules_jvm_external.

This doesn't look like a rules_jvm_external issue, so I shall close this. Please let me know if you'd like me to reopen it.

from rules_jvm_external.

We might want to have same behavior as Gradle : when POM incorrectly specifies a JAR instead of AAR, it will fallback to using the AAR. Thoughts?

from rules_jvm_external.