On Apr 1, 2013, at 6:31, Olivier Lamy <ol...@apache.org> wrote:

> 2013/3/29 Phil Steitz <phil.ste...@gmail.com>:
>> I can't remember if this died with m1, but in the old days we used
>> to get a javadoc error report in maven project reports.  It seems
>> now the only way to tell if there are javadoc errors is to examine
>> the command line output of the javadoc plugin.  Is there a way to
>> get a javadoc error report generated with the site build?
>
> nope m2 plugin doesn't have this feature

That is a shame because it is quite useful.

Gary
>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>
>
>
> --
> Olivier Lamy
> Ecetera: http://ecetera.com.au
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to