hmole
04/13/2019, 6:29 AMbuildSrc
? I tried putting buildSrc
in my buildSrc
🤯 but sadly it didn't work.gildor
04/13/2019, 7:57 AMhmole
04/13/2019, 9:13 AMbuildSrc
scripts itself, not the project scriptsgildor
04/13/2019, 9:14 AMhmole
04/13/2019, 9:15 AMbulidSrc
. It can be multiproject tooproject/buildSrc/module1/build.gradle.kts
project/buildSrc/module2/build.gradle.kts
I want theese build files to be able to reference dependency notation in a typesafe waygildor
04/13/2019, 9:35 AMhmole
04/14/2019, 5:38 AMgildor
04/14/2019, 1:00 PMhmole
04/14/2019, 6:48 PMbuildSrc
code. For example I have 2 modules that generate code and both use kotlinpoet
as a dependency. One is generic for android, and other is a very specific to my workplace build infrastructure. Of course it makes sense to put them in different modules. Now both build.gradle.kts
of these modules have a dependency on com.squareup:kotlinpoet:1.2.0
. You see how the dependency notation is duplicated between files? That's what my original question refers to - how to avoid it?gildor
04/14/2019, 11:18 PMof course it makes sense to put then in different modulesOr just to different plugins
hmole
04/15/2019, 5:32 AMbuildSrc
modules, not sources of buildSrc
modules. That's why I was talking about "buildSrc inside buildSrc"gildor
04/15/2019, 5:35 AMhmole
04/15/2019, 6:09 AMgildor
04/15/2019, 6:14 AMhmole
04/15/2019, 6:45 AMgildor
04/15/2019, 6:47 AM