In attempts to make a Settings plugin it seems there is no access to the
buildscript for adding repositories and things to the classpath in order to
apply an additional Settings plugin or do other fun stuff.
I have something that works as an apply: script, but I really would like to
make it a versioned settings plugin so there is not a need to hit the network
on every build invocation to check that the versioned script is "current".
Even looking at internal objects, it doesn't seem to be readily possible to
adjust the settings classpath for applying plugins.
There is a huge amount of boilerplate in the Settings script that I have now,
that applies a Settings plugin and configures several project repositories and
plugin applications.
In short, the current script does the below steps:
[1] Configure buildscript and classpath for settings to apply the other
Settings plugin
[2] Bring class names into scope to avoid missing property 'com' for package
com.something.plugin.PluginClass
[3] Apply the other Settings plugin
[4] Configure buildscript and classpath for all projects to easily apply other
plugins
[5] Apply some plugins directly to the rootProject before any other plugins
will be applied
I can make all the steps work in a proper plugin except for Step 1.
Step 2 at the moment requires the exact classname and direct imports of the
Plugin classes, so it's not ideal, but I haven't found a way to dynamically
work from a Class object, but I'm sure there must be one. Step 2 shouldn't be
required, but somehow the plugin-by-id stuff isn't initialized at this point.
buildscript {
repositories {
maven { url 'http://some-repo' }
}
dependencies {
classpath aSettingsPluginArtifactNotation
classpath aRootProjectPluginArtifactNotation
classpath bRootProjectPluginArtifactNotation
}
}
// NOTE: Cannot apply plugins by name at this point, that magic happens later,
so have to
// explicitly import plugin classes for apply purposes to settings and
rootProject
// to ensure they happen before any other plugins take effect
import settings.plugin.PluginClass
import project.plugin.PluginClass
import project.plugin.PluginClass2
settings.apply(plugin: settings.plugin.PluginClass)
gradle.projectsLoaded { afterProjectsLoadedGradle ->
afterProjectsLoadedGradle.rootProject.allprojects {
buildscript {
repositories {
maven { url 'url1' }
maven { url 'url2' }
maven { url 'url2' }
}
dependencies {
classpath artifactNotation1
classpath artifactNotation2
classpath artifactNotation3
classpath artifactNotation4
}
}
afterProjectsLoadedGradle.rootProject {
apply plugin: project.plugin.PluginClass
apply plugin: project.plugin.PluginClass2
}
}
Maybe this isn't the best solution, but there are issues with attempting to
build our own custom distribution of gradle with init scripts.
Again, the current solution works, but a proper plugin feels more correct, and
the network call for the apply from: url is a performance hit every single time
a build is run.
Thoughts?
-Spencer
