On 11/02/10 4:02 AM, Nacho Coloma wrote:
Hi, I wanted to share some insight that is more or less related to this thread. The new plugin system is quite awesome. It gives you all the power to reuse gradle scripts seamlessly, but it is also easy for it to get a bit out of control. Take for example the set of plugins that we have developed to scratch our very own itch: https://loom.svn.sourceforge.net/svnroot/loom/shared/trunk/ We are handling near 10-15 projects that are being migrated to gradle right now. As such, code reuse is a big deal, but master was not cutting it, so we started working with gradle-0.9 and the new plugin system. So far, so good. Once we got started, we quite soon started making our own bugfixes: adding providedCompile, creating a javadoc and sources artifacts for our maven deployments, copying the jar files to be included into eclipse... Suffice to say that this folder is the result of less than one month working with it. This is just to point out that once 0.9 gets out, the same will be happening a lot. It would be a good idea to keep track of all the goodies out there, maybe even pick up the ones that should make it into gradle.
This is good feedback. Thanks. Right now, the cookbook lists plugins that we know of: http://docs.codehaus.org/display/GRADLE/Cookbook#Cookbook-plugins I think this probably should be a separate wiki page. We could also take the code snippets in the cook book and move them to somewhere like github, so that you can use them in your build by referring to them by URL. For stuff to migrate into Gradle, people should raise a JIRA issue and we'll look at it. -- Adam Murdoch Gradle Developer http://www.gradle.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
