Is it possible to create a custom buildsrc in Grad...
# gradlen
napperley
07/31/2018, 2:22 AMIs it possible to create a custom buildsrc in Gradle 4.9 using the Kotlin DSL?
a
alex2069
07/31/2018, 2:24 AMYes
alex2069
07/31/2018, 2:24 AMalex2069
07/31/2018, 2:25 AMThat's using 4.9-RC-1
alex2069
07/31/2018, 2:27 AMAnd various code stuffs: https://github.com/NextFaze/dev-fun/tree/master/buildSrc/src/main/kotlin
alex2069
07/31/2018, 2:28 AMThere are still some weird issues/limitations with cross-project (as in "gradle project") class loaders though
n
napperley
07/31/2018, 2:52 AMSeems that buildSrc in the root project isn't accessible in sub projects 🙁.
a
alex2069
07/31/2018, 2:55 AMIt is and isn't - I declare a lot of functions in my buildSrc that are used in the subprojects
alex2069
07/31/2018, 2:55 AMBut there are some limitions with plugins and classloaders (it's a known issue that's being addressed)
alex2069
07/31/2018, 2:57 AMalex2069
07/31/2018, 2:58 AMI had to make
configureAndroidLibn
napperley
07/31/2018, 2:59 AMTrying to make the following accessible from the buildSrc in all projects:
Copy code
object Version {
val kotlin = "1.2.51"
val dokka = "0.9.14"
}a
alex2069
07/31/2018, 3:02 AMYea that should be fine.
My dependency declarations:
https://github.com/NextFaze/dev-fun/blob/master/buildSrc/src/main/kotlin/dependencies.kt
Usage is as expected in subproject `api(Dependency.supportAppCompat)`:
https://github.com/NextFaze/dev-fun/blob/master/devfun-menu/build.gradle.kts#L26
alex2069
07/31/2018, 3:02 AMOh, one thing I would suggest is to not use a package in your
buildSrc🆗 1
➕ 1
alex2069
07/31/2018, 3:03 AMThere were some weird issues when trying to reference things in the root project
n
napperley
07/31/2018, 3:13 AMThe buildSrc still isn't accessible in the sub projects, only accessible in the root project.
g
gildor
07/31/2018, 3:32 AM@napperley No, everything should work. Try to build your project. IDE has some problems with buildSrc on dependencies change
n
napperley
07/31/2018, 3:33 AMSo buildSrc dependency issues get resolved by executing the build task?
g
gildor
07/31/2018, 3:35 AMit’s IDE only problem
gildor
07/31/2018, 3:35 AMGive me a minute, I will find this issue
gildor
07/31/2018, 3:35 AMBut we use buildSrc and it works properly for us, just not so smooth as could be
gildor
07/31/2018, 3:36 AMgildor
07/31/2018, 3:36 AMSo build is not enough, you should somehow trigger build dependencies reloading
gildor
07/31/2018, 3:37 AMWill be fixed in 0.19
gildor
07/31/2018, 3:37 AMThis is issue that I reported about this problem on Kotlin issue tracker
https://youtrack.jetbrains.com/issue/KT-25354
📋 1
👍 1
n
napperley
07/31/2018, 3:56 AMUsing the terminal to run Gradle tasks as a temporary workaround to the issue ☝️.
g
gildor
07/31/2018, 5:01 AM@napperley Just follow workaround from the issue:
One workaround is to make a change in the plugins or buildscript block of the edited script.
gildor
07/31/2018, 5:01 AMAfter that IDE will cache correct version of classpath with your buildSrc depenedencies
n
napperley
08/01/2018, 3:35 AMMade the changes but only some of the errors are resolved. Still end up with the yellow banner appearing.
a
alex2069
08/01/2018, 3:44 AMAre you using Android Studio or IDEA?
alex2069
08/01/2018, 3:44 AMFTR I'm using Android Studio 3.3 Canary 3 and it's generally quite reliable
alex2069
08/01/2018, 3:45 AMIf I change things in the buildSrc project sometimes I need to rebuild and restart the IDE for the warnings/errors to resolve (or using aforementioned workaround)
n
napperley
08/01/2018, 8:31 AMUsing IntelliJ (v2018.2).
2 Views