Cédric Beust ♔ wrote: > > For what it's worth, I have had (and still do) the exact same experience. > > To me, the style guide is a bit similar to trying to learn a language by > learning premade sentences. There is too much emphasis on "how" and not > enough on "why". > .. >
Hello Cedric, Thanks for sharing your thoughts, at least I do not feel lonely :-) Had I found your post earlier, I would have joined... I want gradle, too. Used ant for a time and felt the need to use something more convenient and powerful, but maven has always taken me aback. If I have to learn something new anyway I decided on gradle to be that thing. (Just a side note, when doing the same with a testing framework TestNG was (and still is) the winner :-) I feel the same with the keyword thing. Although the concepts like configures, dependencies are more or less explained and there are simple examples, many times that is not enough. The many ways of doing things is disturbing for a beginner. I do not know what is simply just another option or something that cannot be done otherwise. (One such thing was the possibility to use simple jar name for dependency in case of a local repository. Later when I found useful using Lists for defining repo dirs, jar naming ceased to work, had to change to artifact only notation). Nevertheless, I would like to thank the people of gradle for their great work! What I say is just a voice of one of their "customer". I am sure they know that when interest in their product is getting high the barrier to it becomes immediately visible for many of us. Thanks! -- View this message in context: http://old.nabble.com/where-to-start-for-a-beginner-tp26741219p26748435.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
