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.
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
Le 01/04/2013 13:49, Gary Gregory a écrit :
That is a shame because it is quite useful.
Well, that depends on the target audience. For the developers it's
indeed useful, but as part of the site for the average users it isn't
very interesting.
Emmanuel Bourg
smime.p7s
Description: Signature
Artifacts and site look good. When building with Java 1.5 under Windows
7, I get the output below. A build with Java 1.7 is successful.
IIRC I had similar results for the last release with JDK 1.5. So I
assume this is not a blocker, and here is my +1
Oliver
Failed tests:
With 3 binding votes (Gary, Phil, Mladen) and one non-binding
vote (Ognjen) I declare this vote as passed.
On 03/28/2013 02:12 PM, Mladen Turk wrote:
Please vote (vote will remain open for at least 72 hours).
Regards
--
^TM
