Was playing around with GWT and found it a little annoying using either
shell scripts or cumbersome ant targets to compile the code, so I've
written an Ant task extension, and made it available on my site
http://www.nsshutdown.com/viewcvs/viewcvs.cgi/GWTAntTasks/
It essentially creates a new ant task gwtcompile, allowing you to
simply have targets like:
<target name="compile">
<gwtcompile src="src" out="www" module="com.pjaol.test"
loglevel="error"/>
</target>
I'll contribute it to the google repository, once I have time to deal
with the paper work and of course
if google will accept it. But please feel free to use it in the mean
time.
Thanks
Patrick
Scott Stirling
Framingham, MA
Here is a step that simply makes it easier for developers, an addition
to the tool that makes it simpler. Is that not the Zen of GWT?
A standard java task for compiling looks like:
<java classpathref="gwt.path" fork="true"
classname="com.google.gwt.dev.GWTCompiler">
<jvmarg line="-XstartOnFirstThread"/>
<arg line="-out www/"/>
<arg line="com.pjaol.test"/>
</java>
This simply takes the hassle out of it, and reduces it down to
<gwtcompile src="src" out="www" module="com.pjaol.test" >
Thanks
Patrick
I don't think that maxim is as useful in software dev as is Occam's Razor.
> A standard java task for compiling looks like:
> <java classpathref="gwt.path" fork="true"
> classname="com.google.gwt.dev.GWTCompiler">
> <jvmarg line="-XstartOnFirstThread"/>
> <arg line="-out www/"/>
> <arg line="com.pjaol.test"/>
> </java>
>
> This simply takes the hassle out of it, and reduces it down to
> <gwtcompile src="src" out="www" module="com.pjaol.test" >
I dislike it because it needlessly removes one's ability to inspect
the command line parameters, such as the JVM -X option you passed.
Custom tasks in Ant were once very useful as the *only* way to
seriously extend Ant. But then a canon of custom tasks emerged and
tasks like <macrodef>, <script>, <java> and <exec> allow you to do
most things in Ant without writing a task that needs to be compiled,
deployed and configured.
Scott Stirling
Framingham, MA
I dislike it because it needlessly removes one's ability to inspect
the command line parameters, such as the JVM -X option you passed.
Custom tasks in Ant were once very useful as the *only* way to
seriously extend Ant. But then a canon of custom tasks emerged and
tasks like <macrodef>, <script>, <java> and <exec> allow you to do
most things in Ant without writing a task that needs to be compiled,
deployed and configured.