It seems everyone does have their own favorite style of viewing and writing code. It would be cool if there was some kind of reformatting layer around the configuration management software, so project members wouldn't have to battle it out in the files. Based on the other messages in this thread, it sounds like Maven at least has some kind of style-checker somewhere in the system (build time, I assume). I do think there is value in having one consistent, automatically-enforced style for a project. But, I think it would be ideal for team members to be able to reformat on "check out" to get the code into the style they prefer, and then reformat again on "commit" to match the style chosen for the project. Failing builds due to "style errors" sounds painful without either a) project-wide buy-in on the standard or b) something that will automatically reformat on commits. I assume you can test if your code passes the style-test before committing.
I am sure it would raise some further issues for people when using ViewCVS, responding to line numbers in stack traces from bug reports, etc. But I think people would be happier and code would be prettier overall if such a system were in place. Another big advantage: no need to vaguely describe the code formatting standard for the project, or argue about if a piece of code matches the standard or not. Instead, it is just a program, script, whatever -- however it comes out is the standard. Period. IntelliJ IDEA feature-of-the-day: you can have different style settings for each project. This is nice when your company, your clients, and the open-source projects you work on all have different style standards. -Max ----- Original Message ----- From: "Cedric Dumoulin" <[EMAIL PROTECTED]> To: "Struts Developers List" <[EMAIL PROTECTED]> Sent: Monday, December 16, 2002 1:09 PM Subject: Avoid code reformating ! > > Hi everybody, > > Code formating is an ever ending debate. We, as experienced > developers, all have our preferences. When there is several users as in > Struts, there is a polite rule: do not reformate code of others just > because they don't follow your criteria. > I have discover such reformating in code that I have written. The > problem is that I don't recognize the code anymore, it takes me more > time to do something, and comparisons tools can't work anymore ;-( > I don't want to debate about the "right" or the "best" code formating. > I just ask for the respect of each others. > So, for those having an automatic code formatter, please disable it > when playing with struts code, and resist to the tentation ;-) > > Cedric > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
