Russel Winder-4 wrote:
>
> So until the JavaDoc task is fixed properly, there seems no hope to
> getting rid of the messages. GRADLE-360 sets out one of the issues, but
> there are many others.
>
I won't claim that the javadoc task is now fixed "properly",
but a couple of days ago, I posted a patch in GRADLE-378
that allows Gradle's javadoc task to support many
(but not all) of the options offered by Ant's javadoc.
Specifically:
* access
* additionalParam
* author
* breakIterator
* classPath
* defaultExcludes
* doclet
* docletPath
* encoding
* footer
* group
* header
* helpFile
* link
* linkOffline
* linkSource
* locale
* maxMemory
* overview
* splitIndex
* stylesheetFile
* title
* use
* useExternalFile
* verbose
* version
The good:
* The enhancements seem to work
* I documented them in the Tex-based userguide.
The bad:
* All (not most) args should be suppported.
* I've only done light testing
* No automated tests yet -- sorry.
The ugly:
* I should have re factored the existing javadoc code and based things
on
the 'option' object pattern... but I didn't. Instead, I just
extended the
internal calls to handle all the args. Chalk it up to being new at
both
Gradle & Groovy, and impatient to get something good enough for me
to use ASAP.
Anyway, if someone wants to take a crack at fixing the build's javadoc
warning,
the patch I submitted might be helpful.
Cheers,
- Jon
--
View this message in context:
http://www.nabble.com/Regarding-JavaDoc-etc.-during-Gradle-build-tp21515319p21782582.html
Sent from the gradle-dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
