+1 very good initiative. Kenn
On Fri, Jan 28, 2022 at 7:27 AM Kerry Donny-Clark <[email protected]> wrote: > Sounds great. Is there a Jira issue? Also, are you planning on > implementing this? > > On Thu, Jan 27, 2022 at 9:00 PM Brian Hulette <[email protected]> wrote: > >> I'm +1 for this, it's frustrating to run into issues with >> other toolchains if you're only working in one SDK. Is there any downside? >> >> On Thu, Jan 27, 2022 at 5:56 PM Yichi Zhang <[email protected]> wrote: >> >>> Hi Beam Dev Community, >>> >>> I realized that our beam gradle scripts use task.create() exclusively, >>> for example in BeamModulePlugin.groovy. This has led to some problems, for >>> example if people just want to run a spotlessApply for their java code >>> change they end up also configuring the python and go environment etc which >>> is probably unnecessary, and could even be blocked for quite a while if >>> their environment is missing the toolchain. Gradle recommended using task >>> configuration avoidance api when declaring tasks >>> https://docs.gradle.org/current/userguide/task_configuration_avoidance.html#task_configuration_avoidance(TLDR: >>> swap task.create() with task.register()) thus that the configurations are >>> only evaluated when it is really needed for the task execution. >>> >>> Any opinions on adopting the recommendations? >>> >>> Yichi >>> >>
