First of all, it's done (other than 4 files), touching about 470 source files. It's not just formatting, but making it mostly consistent. The dates have to be left inconsistent and everything else made consistent. Even if that's a good approach, why redo it again?

Maybe that can be used for the tabs issue. There's already a bunch of other solutions proposed on that one. If jalopy is made to format code to a specification and CheckStyle is to check if you formatted code to a spec, why not combine the tools. It could be like fsck, where it comes across errors and then you just choose Y and it fixes the problem for you. :)

Paul

[EMAIL PROTECTED] wrote:

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26077>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.


http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26077

Checkstyle reports -Licenses incorrect





------- Additional Comments From [EMAIL PROTECTED]  2004-01-13 00:36 -------
What's the difference between this and doing
 maven jalopy:format?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to