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. ----- Best regards, Evgeny evgeny-goldin.com -- View this message in context: http://gradle.1045684.n5.nabble.com/Aliasing-commonly-repeated-tasks-combination-tp4513918p4519200.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
