As I was looking at the shared asn1.codec checkstyle errors, I think we should tune it to remove useless errors :
- Line has trailing spaces
- Line is longer than 80 characters. (should set a new limit at 128... We are not anymore using a VT100 terminal to code :) - '{' should be on the previous line : In fact, we selected this format. '{' must be on a new line. - '(' is followed by whitespace. Again, this is a format choice. I would rather get a warning if it's not the case
- ')' is preceded with whitespace. Same as above
- Parameter decoder should be final. I hate this constraints. I know it's a kind of trick to protect the parameter from being modified inside the method, but IMHO, it bloats the methods declaration Now, it may be just me ...

I didn't checked all the reports, but if we tune CheckStyle to change those parameters, we will have hundreds (thousands ?) or removed errors.

wdyt ?


On 5/14/10 10:05 PM, Felix Knecht wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

For interested people

I created for the shared [1] and the apacheds [2] project the report
site for svn trunk.

Apart from the reports about newer versions of
plugins/dependencies/properties following reports may be of a special
interest (each module has the reports on its own):

- - Cobertura Test Coverage
  (e.g.
http://people.apache.org/~felixk/apacheds-docs/apacheds-xdbm-base/cobertura/index.html)

- - Findbugs Report, specially the ones with high priority
   (e.g.
http://people.apache.org/~felixk/apacheds-docs/apacheds-core/findbugs.html).


Regards
Felix

[1] http://people.apache.org/~felixk/shared-docs/
[2] http://people.apache.org/~felixk/apacheds-docs/

PS:
apacheds-docs are still beeing deployed. Hopefully also all available
tomorrow
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvtrRUACgkQ2lZVCB08qHEtBwCfYuinR4dxRBvhrAhf90zhVV9Z
s4gAoK3F82Aj45cfIckFZDZy8SaTd33y
=oIZZ
-----END PGP SIGNATURE-----



--
Regards,
Cordialement,
Emmanuel Lécharny
www.nextury.com


Reply via email to