I also tried this, but unless I overlooked them--there's a lot to
wade through--the maven-checkstyle-plugin does not report the same
warnings that the javadoc commandline tool reports.
E.g. it doesn't tell me about [EMAIL PROTECTED] com.lafros.MissingClass} in my
javadoc comments.
The maven-javadoc-plugin does at least tell you how many such
warnings there are, so I suspect it ought to be possible to write a
modified version that can list them as well.
Has anyone tried this?
Btw, adding a <verbose>true</verbose> doesn't include them.
Rob
On 5 Jul 2006, at 01:47, Julian Wood wrote:
Oops - sorry missed the rest of that thread. I will check out the
checkstyle report.
J
On 4-Jul-06, at 6:32 PM, Julian Wood wrote:
Yes I'm looking for this too. It was a way to make sure that
javadocs were being filled out properly (and to define what
properly was). I also recall a mention of failing builds if
javadocs weren't adequate. Is this around at all?
http://maven.apache.org/maven-1.x/javadoc-warnings-report.html
Thanks,
J
On 12-Apr-06, at 9:15 AM, Paul Spencer wrote:
Wayne,
In general the output of the "verbose" parameter from the javadoc
command.
Examples:
o warning - @return tag has no arguments.
o warning - Tag @see: can't find getCompanyId(java.lang.String)
o warning - The first sentence is interpreted to be:
o warning - @param argument "numberOfDays" is not a parameter
name.
Paul Spencer
Wayne Fay wrote:
What kind of "warnings" did it report exactly??
Wayne
On 4/12/06, Paul Spencer <[EMAIL PROTECTED]> wrote:
Maven 1.0.2 produced a Javadoc warnging report. I have not
found this
in Maven 2.0.x.
Does it exist? If so, where and how is it configured?
Paul Spencer
--
Julian Wood <[EMAIL PROTECTED]>
Software Engineer
Teaching & Learning Centre
University of Calgary
http://tlc.ucalgary.ca
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
