On Sep 9, 2009, at 1:49 AM, Adam Murdoch wrote:
Hi,
I've just committed some changes to the command-line:
1. You can use a partial task name to specify which task to execute.
For example:
gradle cl t
is equivalent to gradle clean test.
2. You can use a camel case abbreviations for task names, similar to
how IDEs allow you to do this with class names:
gradle expDBas intTest
gradle eDB iT
are both equivalent to gradle explodedDistBase integTests
For both these shortcuts:
* Gradle will complain if the name you've specified is ambiguous.
* They work with the -x option: gradle clean build -x iT
* They work at the task name part of a task path: gradle gradle-core:t
* They don't (yet) work with the project part of a task path, ie,
you can't do gradle :g-c:test
This is fantastic.
3. I've also rearranged the output when the build fails. I think
it's clearer, but this is a subjective thing. Let me know if you
like/dislike it.
I like this also very much.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
