Ronen Narkis wrote: > > Hmm I agree maybe a better option would be to commit the init file with > the > project, the thing is that I don't want the user to specify which init > file > to use (the default path is ~/.gradle) so I though to copy it right after > running the wrapper. >
You could tweak the gradlew shell script to always use the committed init.gradle file. Another thing that I think that would be cool is to add gradle to the bin path (.bashrc or in windows to the registry) right after download. Are you talking about gradle or gradlew? For gradlew we can't do this because every build has its own gradlew script. I think you are raising some valid points here, but we haven't figured out yet how to improve on the status quo. -- Peter Niederwieser Developer, Gradle http://www.gradle.org Trainer & Consultant, Gradleware http://www.gradleware.com Creator, Spock Framework http://spockframework.org -- View this message in context: http://gradle.1045684.n5.nabble.com/Gradle-wrapper-post-install-hook-tp4301785p4303082.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
