What happens to 3rd party Gradle dependencies when support for 'compile' is removed at the end of 2018?

Asked Oct 25 '18 at 08:22

Active Oct 25 '18 at 08:22

Viewed 50 times

This is a question I could not really find an answer to. Even though I replaced all compile with implementation in my gradle file, I still get a warning that says

Configuration 'compile' is obsolete and has been replaced with 'implementation' and 'api'.It will be removed at the end of 2018.

Therefore, I assume one or more of my dependencies still use compile instead of implementation.

My questions here would be:

Is replacing all the compile with implementation in our own grade file enough?
Assuming a few of those dependencies are unmaintained and they contain compile, what would be the suggestion to follow, keeping in mind that support for compile will be removed at the end of 2018?

I would appreciate any guidance. Thanks

asked Oct 25 '18 at 08:22

Orcun

first first part of the question: maybe this helps : https://stackoverflow.com/a/49586312/6899896 – M.Ricciuti Oct 25 '18 at 08:26
Thanks but I have tried this before but I still keep getting the annoying warning. – Orcun Oct 25 '18 at 08:27

What happens to 3rd party Gradle dependencies when support for 'compile' is removed at the end of 2018?

0 Answers0