Hi,
I am currently porting a large ant based multi-project build to gradle.
Generally, the process has been very enjoyable, and the build is looking
heaps better. Thank you for creating gradle.
One thing I miss from our ant-based build is the ability to run a
particular target for all projects or for a particular ad-hoc subset of
projects from the top-level project. I'd like to add something like
this to gradle. In particular, I'd like to be able to (optionally)
specify tasks by path (rather than name) on the gradle command-line.
Something like:
gradle :child1:test :child4:test
More specifically, when a name is provided on the command-line, if it
starts with ':', it is treated as a task path, and the task with that
path is executed (along with its dependencies). Otherwise, it is treated
as it is currently, where all tasks with the given name are executed
(with dependencies).
Would it make sense to add this behaviour to gradle? If so, I'd like to
have a go at adding it. Some questions:
- I couldn't find anything much on the web site about contributing to
the project, eg how to provide patches, which jvms are we targeting,
testing, tracking in jira, etc
- Does it make sense to keep the --non-recursive option, as the same
thing would be possible using :task notation?
- Should project default targets be interpreted the same way?
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
