> Having gone through the Checkstyle errors myself fairly recently, I'm > pretty sure there's nothing drastic showing up there, so I'd say > fixing these would be a "nice to have" at best for 1.3.0. In other > words, if someone has a real itch to apply patches to resolve these, > that would be fine, but I'd hardly hold up a 1.3.0 until the > Checkstyle report is clean.
No argument here... I didn't mean to say that 1.3.0 should not be released until all CheckStyle complaints were addressed... I'm going to put some time in to see if I can cut into the number of them before that release happens, but I certainly agree, the release should go forward either way. > (Don't get me wrong - I hate to see Checkstyle / PMD / FindBugs > warnings. But I'd also hate to deny our user base a 1.3.0 build just > because we still have such warnings.) Absolutely :) Especially when the vast majority of them look to be very much non-critical complaints I don't see any reason whatsoever to impact the release. > Martin Cooper Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
