> > Quite a few errors have crept into the code, especially in trunk. Lets
> > all please review checkstyle, findbugs and javadoc warnings before
> > committing changes. That will make it much easier to prepare releases.
> > We can talk about loosening / eliminating checks if we want to; but we
> > should adhere to the ones we keep.
> > 
> > I don't want to sound too whiny here - I make my share of mistakes and I
> > am sure that I will make plenty more.  It just avoids really, really
> > boring cleanup work in the runup to a release if we try to keep the code
> > clean as we commit it.  Thanks in advance!
> 
> Strong +1 here.

In case you were referring to the multiple instances of the same Javadoc
error which I introduced, please note that I signalled the problem in the
MATH-413 issue (point 14). I'd be happy to know the workaround (short of
suppressing the @link).


Gilles

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

Reply via email to