I would also like to know this, I suspect we have to use the old buildscript closure instead or maybe we can use the buildscript closure to set the repository then the new plugins closure will use it. I don’t know yet, I should know soon though.
There are no marker artifacts in that repository yet, so you currently can’t proxy the plugin portal for use with the new DSL. The old answer to use the buildscript block is unfortunately still valid.
buildscript {
repositories {
maven {
url 'http://nexus3-host:8081/repository/maven-public/'
}
}
}
plugins {
id 'net.ltgt.apt' version '0.9'
id 'com.github.hierynomus.license' version '0.13.1'
id 'com.github.ben-manes.versions' version '0.13.0'
}
@novaterata what you showed will still query plugins.gradle.org for the plugin metadata and will not work if that url is blocked. As I said before, mirroring the plugin portal is not yet possible.