Hi, > 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 hmm.... is this really helpful ? I think it will rather make things less readable... You wiil get posts on miling lists like "I run my build with gradle c f b r" and you'll spend hour wondering what does it mean. :) And also the shortcut that works in 0.8 might stop working in 0.9 because new command line switches will be added and it will become ambiguous.
I think people will rather have some aliases made for the most often used functions to speed up the most frequent runs, like gt = gradle test gl = gradle libs etc or have bash completion scripts (btw. we should have one for gradle !) which is even better. -- best regards Tomek Kaczanowski > > 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 > > 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. > > > Adam > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
