On 02/03/2012, at 2:20 PM, Philip Crotwell wrote: > Is there a reason why these are command line args and not tasks?
Generally because they are cross cutting, and not independent pieces of work to be done. That is, they alter Gradle's behaviour in a kind of global way. > 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. Dependency resolution is not atomic, and is done on demand. What you are describing would require introducing something that resolved all of the dependencies for a project. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
