Yes, "module" is definitely a better name. The reason I didn't use it
is that the name "module" was already used by another method (by
InternalProject.getModule, I think), and so the script wouldn't compile
when I used it. Maybe someone more experienced than I knows a way
around that.
Thanks for looking it over, and for your feedback!
On 6/11/11 9:22 AM, Andrew Oberstar wrote:
This looks great!
I'm not sure how attached you are to the "deploy" name for the
configuration that would include WARs. It seems like module is the
official term for those dependencies, so maybe "module" would make a
better for for the configuration name.
http://download.oracle.com/javaee/6/tutorial/doc/bnaby.html
Andy Oberstar
On Mon, Jun 6, 2011 at 11:46 AM, Szczepan Faber <[email protected]
<mailto:[email protected]>> wrote:
Hey,
We've got the first draft of the ear plugin. Feedback is very
welcome. Docs:
http://gradle.org/releases/latest/docs/userguide/ear_plugin.html
http://gradle.org/releases/latest/docs/dsl/org.gradle.api.tasks.bundling.Ear.html
To play with it, update your wrapper properties:
distributionUrl=http\://repo.gradle.org/gradle/distributions/gradle-snapshots/gradle-1.0-milestone-4-20110605214820+0200-bin.zip
<http://repo.gradle.org/gradle/distributions/gradle-snapshots/gradle-1.0-milestone-4-20110605214820+0200-bin.zip>
Special thanks to David Gileadi for his contributions!
Cheers!
--
Szczepan Faber
Principal engineer@gradleware
Lead@mockito
---------------------------------------------------------------------
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
