> removing this limitation is not a high priori...
# gradle
j
removing this limitation is not a high priority because in the long run we want to move away from
buildscript
style classpath specs to
plugins
style dependencies
That won't really work if a plugin needs to resolve a dependency dynamically that is located in mavenCentral.