logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: Applying Jalopy?
Date Mon, 24 Mar 2003 13:51:12 GMT

If there is some help needed with configuration of either jalopy or checkstyle, I'll be glad
to help.  Sorry for contributing the original tasks to the log4j build.xml and then disappearing
;)  An unexpected moved up deadline at work.

To someone else's point: I've found that running checkstyle on an unformatted code base will
result in a ton of errors, probably too many for the report to be meaningful.  However, more
than 80% of these errors tend to be trivial for an automated formatter to fix, e.g. line too
long or keyword order incorrect (final static instead of static final etc.).  So running a
formatter on the entire codebase, just once, before running checkstyle, will remove around
80% of the errors.  Alternatively, checkstyle can be configured to not check these things.

Yoav Shapira
Millennium ChemInformatics

>-----Original Message-----
>From: Oliver Burn [mailto:oliver@puppycrawl.com]
>Sent: Tuesday, March 18, 2003 8:49 PM
>To: Log4J Developers List
>Subject: RE: Applying Jalopy?
>> -----Original Message-----
>> From: Ceki Gülcü [mailto:ceki@qos.ch]
>> Sent: Wednesday, 19 March 2003 05:48
>> To: Log4J Developers List
>> Subject: RE: Applying Jalopy?
>> I have also installed a checkstyle plugin into Eclipse, Unfortunately, I
>> get over 20'000 warnings over log4j source code which renders
>> the tool very
>> much impractical to use. Moreover, I do not see a problem with a large
>> number of the generated warnings. There are probably ways to
>> suppress some
>> of the warnings but I am not familiar enough with Checkstyle to
>> implement
>> the desired customization. To be brutally honest, for the time
>> being I am
>> much more comfortable with applying Jalopy per file or per batch
>> in lieu of
>> battling with gazillions of checkstyle errors. Anyway, I'll battle some
>> more to see if things improve.
>This is always a problem with using a tool like Checkstyle after the
>fact. My personal record is getting 100,000 errors on a project I
>was consulting to.
>One nice feature about the Eclipse Checkstyle plug-in is that you
>can tell it which packages to actually report on. This combined with
>the Eclipse filter functionality lets you control errors very
>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.

To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

View raw message