Hi together,
I understood that there is a semantic difference which is very important to
understand, in order to use gradle properly.
I tried to state, that I am a bit concerned about the little syntactic
difference between adding actions and configuring a task. May I also add that
describing the execution-behaviour of a task is more important to me than
describing its configuration. I therefore think that "task myTask { ... }"
should definitely describe the execution-behaviour.
Kind regards
Matthias
________________________________
From: John Murph [mailto:[email protected]]
Sent: Dienstag, 26. Mai 2009 17:32
To: [email protected]
Subject: Re: [gradle-user] Changes in task definition dsl?
On Tue, May 26, 2009 at 7:04 AM, Pfau, Matthias
<[email protected]<mailto:[email protected]>> wrote:
Hello Hans,
thanks for clearing this up. I just digged into the manual again and saw, that
you described my problem in Example 23.2.
Anyhow, the difference between adding actions to a task and configuring a task
is very small.
Hi Matthias,
When you say the difference is small, which of these do you mean:
1) There is little execution difference between configuring a task and
executing a task. Both closures run, after all, just at slightly different
times.
or
2) There is little syntactic difference between configuring a task and
executing a task. "task myTask { <configure> }" and "task myTask << { <action>
}" are very close.
There was some discussion regarding the new syntax before release of 0.6, and
your clarification on what is concerning you would be helpful.
--
John Murph
Automated Logic Research Team
