Hi Tom,
I feel the same, if you know how to set Eclipse such that it gives me
only usefull warnings, I am all ears.
Currently, it always gives a few warnings for every function with
parameters, and I do not find any way to suppress these warnings.
So I try not to look at them, and switched off checkstyle warnings,
since they drown in the useless ones...
1. revise the coding conventions to something that we'll ALL use (and are
easily supported by our tools) 2. come up with a set of
Eclipse/Emacs/whatever settings that support our conventions 3. enforce
conformance by asking the author to make revisions to non-conforming commits
rather than changing their code for them 4. when reformatting old code,
make the minimal change which will bring the code into conformance 5. Stop
mechanically resolving checkstyle warnings without adding value - this just
masks real problems
(e.g. adding comments like /* Constructor */ or Javadoc @param tags with
no contents)
I thought we agreed on all this, only the tooling does not work, and
some of the less-obeyed conventions are about peanuts, and I even
disagree about some.
E.g. the cookbook says:
«All instance variables are private.
This is not required by the Sun Code Conventions but an additional
requirement for ArgoUML.
This is checked by Checkstyle. »
I like to use protected instance variables. Can I remove this requirement?
Regards,
Michiel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
