[GRADLE-378] Gradle's javadoc task should provide more propreties that allow for finer-grained tuning of Javadoc Created: 29/Jan/09 Updated: 04/Jan/13 Resolved: 14/Mar/09
|Reporter:||Jon Cox||Assignee:||Tom Eyckmans|
The current level of tuning offered by Gradle's javadoc task is inadequate.
Some properties are inherently problematic, like "private" (which is a Groovy keyword),
|Comment by Jon Cox [ 29/Jan/09 ]|
This somewhat clumsily-written patch makes Gradle's javadoc task
Also included in this patch is an update to the TeX-based userguide.
There are a few shortcomings to this patch:
That said, I think this covers the bulk of my own javadoc needs,
After speaking with Hans, I'm guessing that Java-based tests
|Comment by Jon Cox [ 30/Jan/09 ]|
I just took down the prior version of this patch, and am posting
|Comment by Tom Eyckmans [ 23/Feb/09 ]|
I've worked my way through the reference documenation and added all the core javadoc options and the options of the standard doclet.
This is done in a class hierarchy that can be extended in you want to use a different doclet you can plug in your own options class for the options of the doclet you are using.
If you urgently need this functionality you can get it from http://github.com/teyckmans/gradle/commits/javadoc note that this is still dev code and some more testing needs to be done in order to make sure everything is in order.
|Comment by Tom Eyckmans [ 14/Mar/09 ]|
all options the core Javadoc options and all the options of the standard doclet are now available in trunk