> -----Original Message----- > From: Ceki Gülcü [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 19 March 2003 05:48 > To: Log4J Developers List > Subject: RE: Applying Jalopy? > > [snip] > 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 nicely. Regards, Oliver --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
