espresso-contrib 3.0.2-alpha1 packages android.arch.{lifecycle/core} classes [73722050]

Fixed

Bug

Status Update

No update yet.

Description

ga...@google.com

created issue #1

Feb 21, 2018 06:00PM

classes.jar from espresso-contrib aar, version 3.0.2-alpha1, contains copy of android.arch.{lifecycle/core} classes. Duplicate classes might cause issues such as

http://b/73450636, but also, javac compilation might produce faulty output because type lookup depends on classpath ordering. This means that android.arch.lifecycle classes will be resolved from espresso-contrib.jar instead of e.g. android.arch.lifecycle:common:1.0.3.

Is it possible to rename these classes, or to declare dependency on artifacts contain it in the pom file?

Comments

yo...@gmail.com <yo...@gmail.com> #2Feb 21, 2018 10:43PM

this would be nice but given Compose and all other priorities, we are not planning to make any big investments in data binding (support KSP is a very big task).

nk...@google.com <nk...@google.com> Feb 28, 2018 12:14AM

Reassigned to nk...@google.com.

nk...@google.com <nk...@google.com> #3Mar 28, 2018 09:48PM

Marked as fixed.

Makes sense. And is there any way to trigger data binding without kapt plugin, assuming there are no custom binding adapters in given module?

Issue 73722050

Description

Issue summary

Comments

yo...@gmail.com <yo...@gmail.com> #2Feb 21, 2018 10:43PM

nk...@google.com <nk...@google.com> Feb 28, 2018 12:14AM

nk...@google.com <nk...@google.com> #3Mar 28, 2018 09:48PM

Add comment

Issue metadata