This message was deleted.
# community-support
s
This message was deleted.
v
Does it really have to be a "lambda" or similar? It is pretty problematic, especially if you want to support Groovy DSL and Kotlin DSL. The cleaner approach is to have some extension class that has a function and register that as extension, then you can do
myExtension.myFunction()
in the build script. Or maybe an alternative would be to provide a build service that people then can use, much like the
grgit
plugin does to provide you a JGit
Git
instance through a build service.
c
no, not really
what's a build service?
They have various usage vectors. One is to kick up some service like some server you need for some tasks like tests and orderly shut down when no longer needed. Another is to restrict access to some external resource that must not be used by multiple tasks. Another variant of that is to make sure a set of tasks is not running in parallel without imposing any dependency or ordering constraints and also cross-project. Another is to have some build-scoped shared state. A variant of that is that you can also use a build service to properly transport information from the settings script to the build script. ...
Quite useful