I always had trouble with the ant build.
Currently my ant build gets no errors and no warnings and creates
fop.jar though it tells me junit and xmlunit are not found.
Last time I put jars in my fop lib folder for junit and xmlunit it told
me they were found and it wouldn't update the fop jar.
How can I get hundreds or even thousands of warnings from trying to use
the eclipse build project option with the default settings while the ant
build has no errors? Is the ant build too permissive?
I don't know if all this junk (dead code?) is slowing it down or just
using up a little memory on loading the class but it should be cleaned
up though I could agree there are surely more important tasks.
From: Glenn Adams [mailto:gl...@skynav.com]
Sent: Monday, February 21, 2011 2:58 PM
Cc: Eric Douglas
Subject: Re: Solving FindBugs issues [was: Re: svn commit: r1071912 - in
The current trunk shows no warnings during ANT compile. Please make
reference to the current trunk/HEAD as 1.0 is published and history at
It's a different matter with certain IDEs, e.g., Eclipse, which set
their warning levels to a more sensitive level than the ANT build.
Although it would be nice to eliminate such additional warnings, it is
not as high priority IMO as ensuring that new compile, checkstyle, or
findbugs warnings/errors do not appear during ANT builds. At the same
time, warnings that do appear should not automatically be excluded
without careful, manual review.