buildr-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Boisvert <alex.boisv...@gmail.com>
Subject Re: Building JavaDoc for Groovy Project
Date Thu, 18 Nov 2010 17:37:21 GMT
On Thu, Nov 18, 2010 at 9:03 AM, Simon Harrer <simon.harrer@gmail.com>wrote:

> thanks for the Gem. I tried it. However there seems to go something wrong.
>
> All my html files for the classes are stored in the DefaultPackage while
> the
> package html files are correctly created.
>
> After  a little investigation it seems that GroovyDoc only want to have a
> list of source directories instead of a list of source files. Is it
> possible
> to rewrite the doc task for working with source directories instead of the
> comple paths to the source files?
>

Cool, I'll fix that.


> Using the ant script below, everything is created fine.
>
> <project
> name="test" default="doc"
> >
> <target
> name="doc"
> >
>  <taskdef
> name="groovydoc"
> classname="org.codehaus.groovy.ant.Groovydoc"
>
>  classpath="C:/dev/eclipse/plugins/org.codehaus.groovy_1.7.5.xx-20101007-1100-e36-RC2/lib/groovy-all-1.7.5.jar"
> />
> <groovydoc
>  destdir="doc/gapi"
> sourcepath="src/main/java"
> packagenames="**.*"
>  use="true"
> windowtitle="WINDOW_TITLE"
> doctitle="DOC_TITLE"
>  header="HEADER"
> footer="FOOTER"
> private="false"
>  >
> </groovydoc>
> </target>
>
> </project>
>
> Maybe buildr could leverage this ant task for the GroovyDoc creation?
>

We could but it wouldn't save us much, since the Ant task is just a thin
wrapper around the GroovyDoc main class and right now we're calling the main
class directly.   Argument processing ends up being more straightforward.

alex

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message