+1 to prevent adding tasks after DAG is ready
On Tue, Sep 2, 2014 at 6:29 PM, Marcin Erdmann
<marcin.erdm...@proxerd.pl> wrote:
> While working on the new configuration model Luke and I have noticed that we
> are not locking task container after the configuration phase so the
> following does not throw an error (even though it essentially has no useful
> effect):
>
> task foo {
> doFirst {
> tasks.create("bar")
> }
> }
>
> As implemented at the moment tasks references are added to the new
> configuration model based on the task container contents at the end of the
> configuration phase therefore it probably makes sense to prevent any more
> modifications to the container after that point in time.
>
> Any thoughts?
>
> Cheers,
> Marcin
--
Szczepan Faber
Core dev@gradle; Founder@mockito
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
