I agree it may be a pain from time to time :-( Though it helps consistency a bit but I suppose we could only include a few rules (like no tabs, no star imports) and relax most of pure coding style related rules (spaces, braces, etc...)
On 10/20/07, Andreas Schaefer <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Geeks > > I tried to change some stuff in the ServiceMix trunk in order to > resolve a problem. For now I cannot contribute and so I don't care > about the layout of my changes. Sure enough I have a quite different > opinion on how good code should look like and the compilation fails > therefore. So I was wondering if there is a way to compile the trunk > without have to bother with Checkstyle making the compilation fail. > > <rant> > Personally, I have to say that I hate Checkstyle for most part > because if a developer cannot read some else's code then he/she > should look for another job. Every open-source project has a little > bit different format and so one should better deal with it. > Checkstyle can be used to prevent coding practices that are prone to > cause problems like a single line block without curly brackets but > layout is a waste of time, IMHO. > </rant> > > I am not a contributor and so you, the contributors, can do whatever > you want but I would appreciate if you wouldn't bug me as long as I > am not contributing code. > > Thank you - Andy > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (Darwin) > > iD8DBQFHGk3zs4gPTNnP0gkRApWXAJ9bbBTfn56GS/44uFzqDcNu7OVxXQCcDQua > ArQ9dIhCJuq1k6txHhReUEY= > =NnBB > -----END PGP SIGNATURE----- > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
