On 13/12/09 9:10 PM, Russel Winder wrote:
Most of the Gradle effort has been in Java/Groovy compile, jar and zip
creation, distribution and release. Which is fine.
I am investigating using Gradle for website construction. Even though I
use Gant for the moment, the problem is one of ensuring files are up to
date and taking action if they are not. The current Gant script does
all the decision making in code. With SCons the problem is relatively
straightforward using the DAG-based approach -- specify all the
relationships between the files and a command for transform of one file
to another.
Gradle also has a DAG so should be able to do what SCons can do.
However whilst SCons is focused explicitly on files, directories and
relationships, Gradle focuses on tasks and their relationships. It is
not immediately clear to me what the right model is for achieving using
Gradle that which is trivial using SCons.
I am hoping I have just missed the right bit of the manual/user
guide . . .
No, you haven't. But hopefully soon we'll be able to do something like this.
Now that we can declare the input and output files for a task (used for
incremental builds), we can potentially use that same information to
wire up the task dependencies. Hopefully in Gradle 0.10 we will do this.
This starts to shift the focus of the build script from tasks to files.
Which is a much better way of describing about most builds, I think.
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
