Thank you so much! This kind of basics/background/history stuff is covered pretty much nowhere else and it's incredibly helpful to learn anyway to understand existing code.
compile and implementation are not equivalent. Compile/api will add the dependency to both compile/runtime classpaths of a consumer, implementation only adds to the runtime classpath of the consumer. You should just remove this (and provide a replacement if need be) because it's wrong and will needlessly confuse people.
No, you are wrong. impementation is the replacement config for compile. you can check in official gradle documentation also, it also states the same. "implementation (supersedes compile) - used for compilation and runtime"
Thank you so much! This kind of basics/background/history stuff is covered pretty much nowhere else and it's incredibly helpful to learn anyway to understand existing code.
compile and implementation are not equivalent.
Compile/api will add the dependency to both compile/runtime classpaths of a consumer, implementation only adds to the runtime classpath of the consumer.
You should just remove this (and provide a replacement if need be) because it's wrong and will needlessly confuse people.
No, you are wrong. impementation is the replacement config for compile. you can check in official gradle documentation also, it also states the same.
"implementation (supersedes compile) - used for compilation and runtime"