What do you mean it's "in the inheritance chain"? Since Junit 4,
inheriting from a JUnit base class is no longer necessary or desirable.
Those methods are static and are now imported statically. Likewise,
static imports would also be appropriate to use Spring's and Google's
validation code. Based on the feedback thus far, I am sorry we don't
want to follow suit here with the other leaders.
Paul
On 11/30/2009 1:56 AM, Henri Yandell wrote:
So classical OO naming convention.
Class = noun
Method = verb
Validator.validateNotNull versus the non-OO Validate.notNull.
Theoretically - sure. Reality? assertEquals only works in JUnit
because it's in the inheritance chain. I think I'd dislike
Asserter.assertEquals :)
Hen
On Sun, Nov 29, 2009 at 11:36 PM, Paul Benedict<pbened...@apache.org> wrote:
It is a verb, of course, but methods should be verbs. I am only appealing to
the classical naming convention of methods. They do the work; classes don't.
You can't ask a class to validate; you can ask its methods to validate.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
