On Sun, 2009-07-12 at 10:04 +0200, Hans Dockter wrote: > On Jul 12, 2009, at 9:37 AM, Russel Winder wrote: [ . . . ] > > As I understand it, Gradle will always give access to Ant and so will > > always carry a dependency on Ant. > > If you use Gradle the classic way, yes. But we want to make Gradle > very modular in the future. For some embedded use cases it is > important to have as less dependencies as possible. But the main > motivation for the new copy task is not driven by this (see below). > > > Ant has a copy function, so why > > replicate this behaviour? > > The ant.copy task does not provide an API as rich as we would like it > to be. A Gradle copy object should be able to tell for example if it > actually has copied anything (very important for optimizations). The > Ant tasks have not been designed to be used as an API. You just > configure and execute them. The possibility to communicate in the > other direction does mostly not exist or is very weak. Therefore we > are also working on our own native test runners as a replacement for > the Ant tasks we are using at the moment.
That rationale works for me.
Thanks.
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
