Hi Adam,
On Jul 28, 2008, at 10:48 AM, Adam Murdoch wrote:
Hans Dockter wrote:
At the moment you can't produce resonable documentation for Groovy
code. This is a serious issue. So what the Groovy plugin can do is
either generating rather worthless Groovydoc docs for Java and
Groovy classes. Or to generate classic Javadoc for the Java
classes only and Groovydoc for the Groovy classes (some people
might still perceive a value in having those). Both would live in
different folders.
I might change the groovy plugin to add a 'groovydoc' task, rather
than overriding the 'javadoc' task.
I think this makes sense. I just had a look at the Groovy Plugin and
it anyway does not behave as it should I think.
As described in UG chapter 10, a Groovy project can have a main/java
and a main/groovy folder. The first is treated like a normal Java
project, the second may contain mixed Java/Groovy code. Therefore the
Groovy plugin should not remove the javadoc functionality applied
against the main/java folder (what it does now). So we should have a
javadoc running against the Java classes in main/java and main/groovy
and a groovydoc running against the groovy classes in main/groovy.
I have created a Jira: http://jira.codehaus.org/browse/GRADLE-168
- Hans
Adam
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
