|
filtering question: msg#00024java.findbugs.general
Okay, I have just worked my static bug list back down, upgraded to 1.1.1 and worked the list down again. I really like this tool. It has helped me remove so many bugs prior to unit testing and delivery. Thanks a lot. Now, I still have some 45 "bugs" remaining that I consider to be okay even if they are not best practices. For instance, the program has a problem reading a socket so it tries to close it but socket.close() throws an IOException. So what at, I am trashing the socket anyway from a previous error so I ignore the exception. FindBugs does not see it that way though. What would be nice is to give it a preexisting list bugs as a filter to remove all those that are documented and filed away. Hence, I could spot new bugs faster and not waste time with essentially false positives. Any chances on getting a feature like that? -- Al Niessner 818.354.0859 All opinions stated above are mine and do not necessarily reflect those of JPL or NASA. -------- | dS | >= 0 --------
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: [ 1608715 ] New Quick-Fixes for the eclipse plug-in, Peter Friese |
|---|---|
| Next by Date: | Using FindBugs programmatically, Patrick Wolf |
| Previous by Thread: | [ 1608715 ] New Quick-Fixes for the eclipse plug-in, mbusarel |
| Next by Thread: | Using FindBugs programmatically, Patrick Wolf |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |