On Mon, Jan 28, 2013 at 1:44 PM, Ken Sipe <kens...@gmail.com> wrote: > [...] > > Hi Ken! > > No, this was with an installed Gradle. > But I don't really have control of that at Codehaus. > But I can certainly try to configure a shell to run ./gradlew instead. > Which is the right thing to do anyway. > Although the underlying problem might have been present with gradlew as > well, no idea. > > > Yes... That's part of what I was trying to understand as well. Gradlew is > advertised as if it worked once it always works.. Which is the way we want > it:). Let me know if you need any help on moving towards it as well... I > should have time this week. >
Thank you, Ken. Well, the Groovy project is already using the wrapper, so there's nothing particular to do in this area, I think. So it's more on the Bamboo configuration side of things that I need to look up and see how I can update all our build plans to use ./gradlew instead of the Gradle artifactory plugin for building. -- Guillaume Laforge Groovy Project Manager SpringSource, a division of VMware Blog: http://glaforge.appspot.com/ Social: @glaforge <http://twitter.com/glaforge> / Google+<https://plus.google.com/u/0/114130972232398734985/posts>
