This message was deleted.

i think only after understanding these DSL scripts/code, one will be able to feel and appreciate the real power of gradle

switch to kotlin build scripts instead and you'll get a lot more IDE support, this will reveal how the dsl works

@Niels Doucet - i really wish i could move to kotlin DSL especially as we are using intellij idea for dev. But i have to stick to groovy dsl for some more time.. as it's more of an enterprise / work group decision then my individual choice.

you can switch locally to investigate how the dsl works, you don't have to actually roll out the migration if there's anything holding you back for now

i work on java projects almost all the times, even when java was new to me i never struggled with the language its self.. as with java it's more like only one way of representing some thing.. no shortcuts etc in java so it's quite straigh forwards

I really think experiencing it will be a lot more interesting than somebody talking you through an api though...

sure.. i can experiment with kotlin dsl on few projects..

I agree with you though. Groovy meta-programming is too much magic for me too 🙂 My understanding of gradle improved a lot after switching to kotlin dsl (still lots to learn of course)

your exp and suggestion is really motivating to switch to kotlin dsl.. let me see if there is somthing to convert groovy dsl to kotlin dsl

https://docs.gradle.org/current/userguide/migrating_from_groovy_to_kotlin_dsl.html#header <-- this might give you some pointers

that is probably configuring a task named

integrationTest

, of type

Test

. (because this is Groovy and not Kotlin DSL, you have to evaluate the script to know for sure)