You are right Gregory, it's imposible to clean all the checkstyle
violations in one pass. Therefore we desided to do this step by step
when refactoring things. In addition you can configure checkstyle which
violations are errors, warnings, infos or ignored. As it don't make
sense to check test cases that strict than the main codebase we defined
to sets of rules. ATM we only apply strikt checkstyle rules to:
- main/org/castor/.... (without TransactionManager)
- main/org/exolab/castor/jdo/JDOManager
A set of lazier rules is applied to following test directories:
- tests/ctf/....
- tests/ptf/....
- tests/utf/....
We should try to keep this directories as clean as possible and when
refactoring other areas of the code also clean them up to conform to
checkstyle rules.
IMO that's the only to get the whole codebase cleaned up step by step.
Ralf
Gregory Block schrieb:
... oh my god...
Ok, so I've never seen checkstyle before; went and ran it against my
codebase.
So how do you go about 'cleaning up' ~600 files worth of hundreds of
screenfuls of errors??? What do you do for a 'first pass' cleaning run
to get rid of tabbing and formatting errors? There's got to be some
kind of tool that can get rid of the majority of the crap.
What did Castor use when it implemented checkstyle? Elbow grease?
-------------------------------------------------
If you wish to unsubscribe from this list, please send an empty message
to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
