Hi Is there a reason why these are command line args and not tasks?
Personally I would rather say "gradle refreshDependencies" as trying to remember which things need to be prefixed with double dashes seems a pointless distinction from an end user perspective. I guess there are some things that only make sense as CLI "dash" args, but it seems to me that if something can be expressed as a task, it should be. That allows all of these things to participate fully in the task ecosystem instead of being a separate external beast. Suppose I wanted to write a task that did something when the dependencies were refreshed. It would be trivial if refreshDependencies was a task, but maybe impossible if it is only in the CLI. Just my $0.02 Philip On Fri, Mar 2, 2012 at 5:24 AM, Szczepan Faber <[email protected]> wrote: >> > I think I'm leaning towards something a bit more descriptive, e.g.: >> > --refresh-dependencies >> > --recompile-scripts >> > --rerun-tasks > > > +1 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
