Old plugin syntax not working in gradle 4.0

[BrainStone]

A little further research shows that this isn’t working for over 5 years…

How can you use an init script to specify a repo/dependency for a plugin JAR, but allow version to be configured in build's root project?

This question came from Luke’s Enterprise Gradle webinar on 7/31. I think I followed his response during the talk, but wanted to get it documented in the forum just in case. Currently every individual build script we have migrated to Gradle has a boilerplate block at the top to declare the repositories like below: buildscript { repositories { maven { url 'http://....' } } dependencies { classpath 'corp:plugins:1.3.4' } } Not only is this in every build, but in every project of the build:…

Well, at least the plugin block is planned to work outside the build.gradle file sooner or later…