commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31519] - Getting rid of some javadoc warn messages (3.2-dev)
Date Wed, 06 Oct 2004 22:02:32 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31519>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31519

Getting rid of some javadoc warn messages (3.2-dev)





------- Additional Comments From public@ecopatz.de  2004-10-06 22:02 -------
The next patch is related to the BooleanComparator class.

Some public methods in that class refer in their javadoc comments to the private
variable 'trueFirst'.

Since the default package access in the build.xml is set to "protected", the
javadoc generator will not see this private variable and gives warnings. The
result is incomplete documentation (broken sentences...)

But hey, there is the public method #sortsTrueFirst, to which these methods can
refer to.

So, this simple beauty patch just rewrites the javadoc comments a bit.

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


Mime
View raw message