> Oh thanks, was not aware of that. Then I don't understand the discussion > between you and some committers who did not run "gradlew" and used "gradle" > instead. Where was the issue then?
I don't think it was a "discussion" as per having an argument - it was more of a "how does this thing work" type discussion... I thought Hoss was running a "local" install of gradle (he wasn't) and I wanted to point out the "right way" of using the wrapper without fully explaining the underlying problem (which I should have done in the first place). Any new tool and workflow will bring doubts and questions and it'll take some time to find oneself comfortable within its new bounds. I wasn't any different when I started working with gradle. My current understanding of how it works (externally) allows me to be convinced that it's a good, very versatile replacement for ant (or maven). It really is more of a programming language (and ecosystem) more than a rule-based traditional build tool, so it'll take some time to sink in. I think we're in good shape though, even if things are not complete -- the aspect-like structure of the current build allows for isolated, controlled changes, more and more committers are getting the hang of gradle itself. Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
