Peter Johnson wrote:I have not found any way in Eclipse, or in subversion for that matter, to prevent a user from checking in code that does not meet the coding guidelines. For my team, I demand that all checked in code either has no warnings or that any warnings are clearly documented in the code as to why the guidelines could not be followed. Of course, they can always check stuff in anyway but then they will incur my wrath. Most people fix their code mainly to prevent the yellow flags from showing up in the editor.
One possibility is if you use Maven for builds, have it generate the various code review reports and publish them on a web site. Then violators will be caught fairly quickly because everyone can see the coding flaws.
Moral of the story: do not discount peer pressure!
Rob Prime wrote:Moving to our IDEs forum.