On Nov 10, 2008, at 10:13 AM, Russel Winder wrote:
On Mon, 2008-11-10 at 09:42 +0100, Hans Dockter wrote:
[ . . . ]
I always run into this frequently. There is a Gradle multiproject
build where it only occurs if multiple projects are build but not in
the case of a single project sub project build. The reports are still
OK despite this warning. It would be nice to get rid of it but I
don't know how at the moment. When we move away from Ant for this
kind of stuff this will be obsolete anyway.
OK, I'll just ignore it then.
Is the "move away from Ant" and indicator that there is a "move to
XXX"
for some XXX, or is the intention to reimplement all the Ant tasks?
In the long run it would be nice to get rid of the Ant dependency for
all our core tasks. Once we modularize we don't need a big dependency
any longer. And the behavior of the Ant tasks are often not as
flexible as we like.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
