[Eclipse plugin] wrong classpath used to find bugs
GoogleCodeExporter opened this issue · comments
Google Code Exporter commented
AS IS:
In projects, which contains more then one class folder with generated
classes (say one is the default one from Eclipse, another one is temporary
created by ant during deployment task) FindBugs report bugs in both
folders, even if some of folders are not on the class path of the project.
This lead to duplicated time used to search bugs in Eclipse and to wrong
bug markers generated (or to not generated at all).
TO BE:
FindBugs should search for bugs only in class folders which are on the
classpath of Java project.
Using latest FindBugs build from SVN head with Eclipse 3.2.2 on JDK 1.5.
Patch (against head) which solves the problem is attached below.
Original issue reported on code.google.com by andya...@nurfuerspam.de
on 30 Oct 2006 at 10:11
Attachments:
Google Code Exporter commented
Sorry, the first patch didn't work in some special cases (if project name does
not
match the project folder), but here is the better one :o)
BTW is anybody watching this patches/issues page?
regards,
Andrei Loskutov
Original comment by andya...@nurfuerspam.de
on 6 Nov 2006 at 10:18
Attachments:
Google Code Exporter commented
committed your patch to SVN
Original comment by bassc...@gmail.com
on 17 Nov 2006 at 9:36
- Changed state: Fixed