-
Notifications
You must be signed in to change notification settings - Fork 37
Linkage problem: toImmutableSet #46
Comments
This appears to be a true positive. This method exists in the jre verison of Guaa but not the android version we use. |
I do not immediately see how we're pulling this in. |
Can we separate the annotation processor classpath from the compile time classpath? |
Do we have the dependency tree that shows where the dependencies come from? |
mvn dependency:tree doesn't point to any likely culprits: INFO] |
We have a |
Setting optional to true in pom.xml resolves this:
|
Is that in the |
New hypothesis: this isn't a problem in this project at all. Rather it's a problem with the linkage checker rule or the maven enforcer which is somehow mixing classpaths with the project being built. |
This one should be fixed by googleapis/google-auth-library-java#358 which is included in google-auth-library 0.17.3 |
Fixed by #56 |
I tried adding the linkage checker enforcer rule to this project and got this error:
[ERROR] Linkage Checker rule found 1 error. Linkage error report:
(guava-28.1-android.jar) com.google.common.collect.ImmutableSet's method toImmutableSet() is not found;
referenced by 1 class file
com.google.auto.service.processor.AutoServiceProcessor (auto-service-1.0-rc4.jar)
The text was updated successfully, but these errors were encountered: