Hans Dockter wrote:
On Aug 22, 2009, at 12:03 AM, Adam Murdoch wrote:
Hans Dockter wrote:
I know that some some stuff is a bit rough ATM. I just wanted to
submit it rather quick to avoid merge nightmares as much as possible
(including for myself). But of course everything should work.
On Aug 21, 2009, at 1:49 AM, Adam Murdoch wrote:
Hans Dockter wrote:
I have just submitted a new build structure for the Gradle build.
The Gradle build is now a multi-project build with a root project
and two subprojects.
root
- gradle-core (which contains everything except wrapper)
- gradle-wrapper
This is great. It will force us to get multi-project builds working
well for java applications.
Some issues I've seen already:
- The groovydocs don't include anything from gradle-wrapper.
It is Java only. That's why the gradle-wrapper should use the Java
plugin only.
We include the java classes from gradle-core in the groovydoc. We
should either not include any java classes in the groovydoc, or
include all java+groovy in the groovydoc. I think we should include
everything in the groovydoc. As the groovydoc tool improves, this
could become the single API reference.
I think as long as the Groovydoc is not a replacement for javadoc we
might not include any java classes. It is quite a big one to upload
when you do a release. Considering the fact that in particular our
public API will contain less and less groovy classes, I'm not sure if
we should move away from the very robust javadoc.
True. We probably want to aim for the whole API to be Java (it's quite
close now), then the javadoc works well as the complete API reference
and we can ignore the groovydoc altogether.
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
