----- Original Message ----- From: "Jerome Lacoste" <[EMAIL PROTECTED]> To: "Maven Developers List" <[EMAIL PROTECTED]> Sent: Wednesday, May 19, 2004 5:30 PM Subject: Re: cvs commit:maven-components/maven-project/src/test/java/org/apache/maven/project AbstractProjectTestCase.java
> > > Perhaps we can run Jalopy in cvs when we commit some modifications. With > > this method, our code will be always well formatted. > > I'll try to do this for all my business projects. > > Just as a note: the cruisecontrol project adopted a pretty drastic approach: checkstyle is ran before the build. > Meaning that a incorrect style will prevent you from developping. > > I wonder what the cruisecontrol developers think about this enforcement. > > I guess that's something one can adopt at the start of a project but not when the project has many files and probably many inconsistencies. > On the other side, one could always use his own style while developing, and reformat before checkin. That would be less restrictive. > > > And instead of changing automatically the code on the server, I'd rather have an error thrown at commit (rejected commit). > > Might be too costly though with CVS (better with a transaction based SCM tool). 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. Emmanuel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
