On 24/06/2011, at 7:58 AM, evgenyg wrote:
> Yes, I have bunch of batch scripts already, optimizing most of commands
> launched daily, like "m" for "mvn -e clean install" and "gr" for "gradle -S
> --no-color".
>
> But to keep adding those small scripts for each project ever developed with
> Gradle means polluting my command-line space and soon I start running out of
> comfortable and memorable ones :) If "build.gradle" keeps aliases then a)
> they're portable for any platform and b) they're specific for the given
> project only. So "gr f" in one project isn't the same as "gr f" in another
> one.
>
> Honestly, I haven't thought of solution yet, but planned to look into
> feeding the String to GradleMain.
It's quite an interesting idea.
I'm thinking of it as a kind of execution layer on top of direct task
executions. Something like…
targets {
lightweight {
command "build deploy -PnoGroovy -x test -x about"
description "Quick build and deploy"
}
}
or…
targets {
lightweight "build deploy -PnoGroovy -x test -x about"
}
There are a bunch of questions about how these things compose though. What does
the following do?
gradle lightweight test
It may be as simple as expanding each in turn, i.e.…
gradle build deploy -PnoGroovy -x test -x about test
At the very least it is worth opening a ticket for to discuss further.
--
Luke Daley
Principal Engineer, Gradleware
http://gradleware.com
Please vote Gradle for JAX Awards » http://vote.jax-awards.com
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
