The code reformatting tools took care of about half of the the Checkstyle errors, but that is still going to leave a thousand or two per subproject. Most of the remaining errors are Javadoc oversights and other non-functional issues.
Overall, addressing the remaining errors is taking me at least an hour per 100 errors. Since we have several thousand errors, there doesn't seem to be enough cost:benefit to addresss the manual errors for the 1.3.0 release. My suggestion is to run the automatic reformatting toolds on the remaining Action Library subproject, wrap up the notes, and call it a release. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
