Some Issues w/ a green install of Checkstyle 5.0 beta

Tim Visher <[email protected]> Wed, 15 Apr 2009 12:07:43 -0400
Newsgroups gmane.comp.java.audit.checkstyle.user
Message-ID <[email protected]>
Hey Everyone,

I have several issues regarding my team's use of Checkstyle so I'm
hoping that someone on the lists can help me resolve them.

1. For some reason the Checkstyle report is doubling all file output.
On one of the report sections it reports 0 violations and on the other
it reports the real violations findings.  I'd like it to only report
once per file and only if that file has violations.

2. We do pretty standard Javadoc comments such as

    /**
     * Example example example...
     *
     * @author example
     */

This is standard Eclipse procedure and every other IDE/Editor that I
know of that does Javadoc comments formats things this way.  The
problem is that Checkstyle seems to believe that the ' * ' is a line
that contains trailing spaces, which of course it is, but that by no
means invalidates it's format.  I couldn't find a specific rule in the
sun-checks.xml file that dealt with javadoc comments and none of the
white space rules appear to indicate that they check after a *.  Also,
 a quick google search only appeared to turn up violations of this
rule in other projects.  Is there any way to get this to stop being
reported/checked?

Thanks in advance!

-- 

In Christ,

Timmy V.

http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com