On Wednesday 14 April 2010 12:57:41, Hans Dockter wrote:
> Sorry for the late response.
No problem at all.
> What you can do is to reconfigure the assemble task. For example:
>
> assemble.dependsOn tasks.withType(Zip).matching { task -> task.name !=
> 'someName' }
>
> or
>
> assemble dependsOn jar1, jar2
I have to beg your pardon, but I went back to ant.
Task sequencing (beside dependency handling) for me is a must have - and I
finally found my error with ant(, so my builds now work without warnings).
For example, when I do my builds during development, I'd like incremental
builds, but when I do integration tests or build a release, I want
the "clean" task to be executed before the build. So I don't want to add a
dependency of clean to build ...
I didn't find out, how to do that kindof sequencing with gradle, so I have to
wait, until gradle will support those things.
Currently my build is stable so I can focus on my errors in my own code.
Even so I use ant, I'm stil convinced, that gradle will be the right tool for
me (some day in future), but not right now, not yet. So I'll keep on reading
the mails and will give gradle a next try, when support for arbitrary task
assembling has grown.
kind regards
Geronimo
P.S. I nearly couldn't beleive it, but ant executes the perl-job (0,5s) using
0.7s - whereas gradle took 10s for that job.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
