Hi, I think we should consider what to do about this at some point. Groovydoc just doesn't cut it and having the API doc spread over two places is no good.
I think we have three options: 1. Only use Java for any public API (i.e. anything that ends up in the api docs) 2. Fix Groovydoc so that it can replace our Javadoc 3. Invent something new #1 is the “easiest” I guess, but it doesn't solve the problem for our users. I'm not sure we can say: “if you want decent API doc, implement in Java”. One way to sidestep this is to advocate the use of interfaces for the public API, but this breaks down for tasks at least (for now). I'm not suggesting we do anything right now, but I wouldn't mind having an idea of where we are going with this. -- Luke Daley Principal Engineer, Gradleware http://gradleware.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
