Compatibility with Guava 22.0-android
See original GitHub issueIt seems that Dagger 2.11 is not compatible with Guava 22.0-android due to the loss of methods like SetMultimap.forEach
. When compiling an Android project with both libraries I’m receiving the following error. Will there be an effort to stay compatible with the new *-android line of Guava releases?
Error:Execution failed for task ':app:compileDebugJavaWithJavac'.
> java.lang.NoSuchMethodError: com.google.common.collect.SetMultimap.forEach(Ljava/util/function/BiConsumer;)V
Issue Analytics
- State:
- Created 6 years ago
- Comments:10
Top Results From Across the Web
Upgrading Guava dependency to Guava 22 - Google Groups
'com.google.guava:guava:22.0-android' is a compatible subset and works on Android. It would be nice to see the bitcoinj dependency updated to a more recent...
Read more >Annotation Type GwtCompatible - Guava
When applied to a method, the return type of the method is GWT compatible. It's useful to indicate that an instance created by...
Read more >Beta (Guava: Google Core Libraries for Java 22.0-rc1-android API)
An API bearing this annotation is exempt from any compatibility guarantees made by its containing library. Note that the presence of this annotation...
Read more >Relationship between "Guava" and "Guava for Android" in ...
the "Android" flavor, which omits those methods so that it is compatible with older versions of Android and with Java 7. Each "flavor"...
Read more >android - Duplicate class com.google.common.util.concurrent ...
implementation 'com.google.guava:listenablefuture:9999.0-empty-to-avoid-conflict-with-guava'. This works but I encountered another issue- ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The annotation processor classpath should be separate from the compile time classpath. I presume you’re getting this error because you have a
compile
dep on guava-android; if so, can you add anannotationProcessor 'com.google.guava:guava:22.0
dep too? If that fixes it, we should update our docsI think you could also set
android.defaultConfig.javaCompileOptions.annotationProcessorOptions.includeCompileClasspath
tofalse
.