> An other approach is to change automatically the code on the server with a > cron like this every day: > - checkout the code > - run jalopy or other code formatter > - checkin all changes with [Maven formatter] in message. > > With this process, we'll have only files checkin in the day that will be > reformating.
Problem I see with that is: if I work on a branch where the code is not clean, this automatic process may introduce merge conflicts. Of course these conflicts can appear by manual style changes, but they are less likely to. I think I would rather provide the option to the developers to clean their code before checkin, and make it sure that it is a required practice. People here should be smart enough to run checkstyle task/goal before submitting a patch! I just don't trust automatic code changes... But after all, that's just my humble opinion, and as I don't have code in the tree yet, you can just discard it :) Jerome --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
