On Fri, May 7, 2010 at 09:58, mjparme <[email protected]> wrote: > > > > Adam Murdoch-2 wrote: > > > > It is, however, a bit awkward to use the javadoc to write a build > > script. Gradle relies heavily on the Groovy DSL goodness, and also on > > dynamic nature of Groovy. Both of these make it difficult for a newcomer > > to figure out what's going on, I think. > > > > I will vouch for the fact that it does take a bit for a newcomer to figure > out what is going on:-) > > The User Guide is great at explaining concepts and gives you idea of how > things work. However, it is a little short on details (like attributes > available for a task of Type: jar). > > I also found it was helpful to be familiar with Groovy. Gradle is making > more sense now since I went and read the Groovy documentation and messed > with it a little bit. > > Out of curiosity where would the Java/Groovy doc be that explains the task > of type Jar? I have looked and I just can't find it. >
This is where things get a little weird. Javadoc doesn't include Groovy classes (naturally) and Groovydoc does a pretty poor job of trying to combine both groovydoc and javadoc, so you have to look in both. Jar is actually a Groovy class, so you have to look in the Groovydocs. > -- > View this message in context: > http://old.nabble.com/What-options-are-available-for-a-Jar-task--tp28478492p28488006.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 > > > -- Jason Porter Software Engineer Open Source Advocate PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu
