Fixed
Status Update
No update yet.
Comments
ra...@google.com
ap...@google.com
I don't think #1 makes a lot of sense. There are already potentially libraries out there without that metadata.
#2 makes the most sense to me, but in case we cannot be 100% reliable we should allow blacklisting libraries as described in #3. This should probably be handled globally for a project (in gradle.properpies rather than in the DSL)
#2 makes the most sense to me, but in case we cannot be 100% reliable we should allow blacklisting libraries as described in #3. This should probably be handled globally for a project (in gradle.properpies rather than in the DSL)
ga...@gmail.com
As I have mentioned I don't think there is a silver bullet. #2 does not work on 100% and #1 will take time before devs will provide the metadata. #3 is in my opinion very important to introduce asap, as the developers have no way how to workaround it at this stage. Also in the future there can be any other issue and there is nothing wrong in doing #3 until we figure out something robust (or for instance finally migrate work manager and navigation to androidx that would make #2 a feasible solution).
Description
Version used: 2.0.1 and 2.1.0-alpha02
Currently workmanager-runtime has a dependency on androidx.lifecycle:lifecycle-extensions. The only two classes in that artifact are ViewModelProviders and ViewModelStores which both aren't used by WorkManager. It would be great if you could change the dependency to what you actually need, for example androidx.lifecycle:lifecycle-livedata-core or androidx.lifecycle:lifecycle-livedata.