Howdy, First off let me say well done on Gradle, it looks great. I tried buildr a while back but couldn't get it to work due to some weird issues on my G5 Mac with one of it's ruby dependencies. No such trouble with gradle.
I'm still a newbie but I have managed to write a basic plugin to build my GWT projects. This has gone pretty well with 0.5.2; I tried migrating to the latest 0.6 snapshot but had some problems and have decided to revert to 0.5.2 till 0.6 has a little more documentation. In 0.6.x it seems that the install task of the maven plugin won't work unless the war plugin is also used (i.e. the war plugin defines the providedCompile and providedRuntime configurations). Using the war plugin however results in my project creating a war instead of a jar which is not what I want. On a similar note, when writing my GWT plugin (for 0.5.2) it would have been nice to use the 'provided' configurations without requiring the use of the war plugin. This is particularly the case when developing a GWT library that needs to be released as a jar but still needs to define 'providedCompile' dependencies (e.g. gwt-user.jar, gwt-dev-xxx.jar etc). Given that, would it make sense for the 'provided' configurations to be defined by the java plugin? Also, I know 0.6 is still in development but simple things like changing the location of my local maven repository or deploying to and external repository wasn't obvisous. It would be great if the samples (or documentation) had examples of just the basics (for newbies like me). e.g. changing the location of your local maven repo, deploying to a maven repository, deploying to an ivy repository etc. Thanks and cheers Andrew
