Steve,
Thanks for the reminder. We turned on javadoc warnings so we could see what
was missing. Now we have all the public APIs documented, so we don't need to
see that all the tests and internal classes don't have javadoc. I've turned
the warnings off in CVS. Once I get confirmation from Johannes that the
Suite constructor fix works for him I'll upload another beta.
Cheers,
Kent Beck
Three Rivers Institute
_____
From:
junit@... [mailto:
junit@...] On Behalf Of
Steve Freeman
Sent: Wednesday, June 25, 2008 11:42 PM
To:
junit@...
Subject: [junit] Nitpick: Eclipse warnings
The Eclipse project for jUnit appears to be set up to have project-
specific settings for things like code warnings. As configured, the
project is not clean of "yellows", such as warnings about missing
javadoc comments. Can I suggest either fixing the problems or turning
off the warnings so that the project is clean?
S.
Steve Freeman
http://www.mockobje <
http://www.mockobjects.com> cts.com
Winner of the Agile Alliance Gordon Pask award 2006
[Non-text portions of this message have been removed]
