On 10/24/2010 8:01 PM, Adam Murdoch wrote:
Some differences:
1. A jar can contribute classes to the applying build script's
classpath. A script cannot. For example, the jar might contain a custom
task implementation which the build script can use. Similarly, the jar
might contain plugin implementations which the build script can apply.
BTW, speaking to this difference in particular I thought I would point
out that your work-around to my similar problem worked perfectly for
creating custom task classes in a script plug-in.
Meaning, in my Xslt plug-in script, I was able to put:
project.Xslt = Xslt.class
...and it allows me to then create tasks of type Xslt.
Not as flexible as the way jars can provide classes but a nice stop-gap
for when a script-based plug-in is otherwise easier and/or more
appropriate and the 'contribute classes' thing is the only issue.
For reference in case anyone is wondering what the Xslt plug-in is:
http://docs.codehaus.org/display/GRADLE/Plugins#Plugins-XsltPlugin
-Paul
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
