I am the author of the Android plugin for Gradle, and I have added the
Android plugin information to http://gradle.codehaus.org/Plugins
However, it seems to me that it is more difficult than it should be for
users to use plugins that are not distributed with the Gradle core. For
example, for someone to use my Android plugin requires all of this
Gradle code:
buildscript {
repositories {
mavenRepo urls: 'http://jvoegele.com/maven2/'
}
dependencies {
classpath 'com.jvoegele.gradle.plugins:android-plugin:0.8'
}
}
apply plugin: com.jvoegele.gradle.plugins.android.AndroidPlugin
Whereas, for any plugin distributed with the Gradle core, it is as
simple as:
apply plugin: 'scala'
I would like to have some sort of well-known plugin repository that
Gradle knows about by default and can search for plugins without
requiring the user to declare the repository in their build.gradle file.
Furthermore, I would like for this plugin repository to map simple names
(e.g. "android") to fully-qualified plugin names (e.g.
"com.jvoegele.gradle.plugins.android.AndroidPlugin").
Is anything like this in the works? Is there anything I can do to help
make such a plugin repository a reality?
--
Jason Voegele
philosophy:
Unintelligible answers to insoluble problems.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
