I'm sitting in IRC with Steve Ebersole trying the best I can to answer questions about plugin development. Having not written one myself, but having looked at the code for some plugins I have to say that starting and understanding how to create a new Plugin and make use of things like upToDate checking, configuration, caching (which I don't know if there is a cache) is exceptionally cumbersome.
Those of us that would like to write plugins really need a plugin developer doc that takes us through various use cases from basic (probably not as basic is "Hello World") to more advanced. Other things to include would be setting up the classpath to include gradle / groovy, including third party jars and packaging it all up to be put out in a repo, a better explanation of methods and annotations for task and plugin development, and probably others I'm not thinking of :) As of right now the standard has been hang out in the mailing lists, google for tutorials that are probably out of date, or read the gradle code itself. None of these are really great options, especially as Gradle starts to become more widely adopted. I don't know if it's too much to ask, but a guide of this sort would be extremely valuable at the 0.9 release. -- Jason Porter Software Engineer Open Source Advocate PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu
