I noticed that the dependencyUpdates task (e.g. when added via global init script) is configured regardless of any task avoidance being used. This is caused by the usage of tasks.findByName() that was introduced with https://github.com/ben-manes/gradle-versions-plugin/pull/504 .
Eventually this causes an overhead by using Kotlin reflection in DependencyUpdatesTask.callIncompatibleWithConfigurationCache.
A workaround for this is to use tasks.getNames().contains().
Hi,
I noticed that the
dependencyUpdates
task (e.g. when added via global init script) is configured regardless of any task avoidance being used. This is caused by the usage oftasks.findByName()
that was introduced with https://github.com/ben-manes/gradle-versions-plugin/pull/504 .Eventually this causes an overhead by using Kotlin reflection in
DependencyUpdatesTask.callIncompatibleWithConfigurationCache
.A workaround for this is to use
tasks.getNames().contains()
.Let me know what you think. Cheers, Christoph