jermainedilao
03/05/2018, 12:36 AMgildor
03/05/2018, 2:26 AMjermainedilao
03/05/2018, 3:08 AMgildor
03/05/2018, 3:09 AMimplementation
with api
in your domainimplementation
dependency hidden from consumer of module with this dependency, it’s special feature of Gradle that allows to use some dependency only internally for some module, without leak abstractions. But if some module expose some type of dependency, you should use api instead.jermainedilao
03/05/2018, 3:15 AMimplementation project(':domain')
in my data build.gradle i will use this api project(':domain')
?gildor
03/05/2018, 3:16 AMapp
module you still use implementation
jermainedilao
03/05/2018, 3:16 AMgildor
03/05/2018, 3:19 AMimplementation
, it allows you in the future remove or replace this dependency and don’t worry that some consumer used it.
- If module uses dependency and expose some types/classes of this dependency to own consumers, use api
. In this case dependency public API now part of your module public APIjermainedilao
03/05/2018, 3:31 AMapply plugin: 'kotlin'
line is missing. Build, and voila. Build succeeded. Thanks so much for the input! I learned something new today.gildor
03/05/2018, 3:33 AMjermainedilao
03/05/2018, 3:35 AMcompileDebugKotlin
was my only clueJames Coggan
03/06/2018, 1:04 PM