Hi Perhaps a related thought, at one point in the pre0.9 timeframe, you could do something like this:
apply url: 'http://github.com/hansd/huglins/raw/master/fatjar.gradle' but that seems to no longer work in the 0.9-preview-1. It seems like that the ideal situation would be for the plugin to be specified by a url, with the directory on the other end being a standard gradle layout and gradle being able to find all the info it needs from that in much the same way that you can dump extra build scripts into buildSrc and have them just work. If the URL thing worked, then a nice variation would be for the URL to be to a web based version control, so that you can easily point to the latest version if that is what you want, or stay with an earlier branch/tag/version if that is what you need. I think that should be doable with git and/or mercurial, but I am new to both so I don't really know. Perhaps having gradle run 'git pill http://my.big.url/abc/pliginXYZ tag .gradle/plugins/pluginXYZ ' internally? Not sure if this doable and I haven't had coffee yet this morning, so just my $0.02. Philip On Fri, Apr 23, 2010 at 8:01 AM, Jason Voegele <[email protected]> wrote: > 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 > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
