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.
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. Ronen On Thu, Apr 14, 2011 at 3:47 PM, Peter Niederwieser <[email protected]>wrote: > > Ronen Narkis wrote: > > > > I really like to use the wrapper for installing Gradle on dev machines, > > still the only part im missing is the ability to customize the > > installation > > (like for example download an init file from artifactory and placing it > > under ~/.gradle) > > > > The wrapper is a per-project concept, so I would be hesitant to install a > global (per-user) init.gradle along with it. What exactly are you trying to > achieve? There may be a better way. For example, you could have a > per-project init.gradle that gets committed to source control. > > -- > 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-tp4301785p4302919.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 > > >
