FindBugs looks for bugs in Java programs. It is based on the concept of bug patterns. A bug pattern is a code idiom that is often an error. Bug patterns arise for a variety of reasons:
Difficult language features
Misunderstood API methods
Misunderstood invariants when code is modified during maintenance
Garden variety mistakes: typos, use of the wrong boolean operator
FindBugs uses static analysis to inspect Java bytecode for occurrences of bug patterns. We have found that FindBugs finds real errors in most Java software. Because its analysis is sometimes imprecise, FindBugs can report false warnings, which are warnings that do not indicate real errors. In practice, the rate of false warnings reported by FindBugs is generally less than 50%.
FindBugs is free software, available under the terms of the Lesser GNU Public License. It is written in Java, and can be run with any virtual machine compatible with Sun's JDK 1.4. It can analyze programs written for any version of Java. FindBugs was originally developed by Bill Pugh. It is maintained by Bill Pugh, David Hovemeyer, and a team of volunteers.
FindBugs uses BCEL to analyze Java bytecode. It uses dom4j for XML manipulation. ~ Source :http://mojo.codehaus.org/findbugs-maven-plugin/
Difficult language features
Misunderstood API methods
Misunderstood invariants when code is modified during maintenance
Garden variety mistakes: typos, use of the wrong boolean operator
FindBugs uses static analysis to inspect Java bytecode for occurrences of bug patterns. We have found that FindBugs finds real errors in most Java software. Because its analysis is sometimes imprecise, FindBugs can report false warnings, which are warnings that do not indicate real errors. In practice, the rate of false warnings reported by FindBugs is generally less than 50%.
FindBugs is free software, available under the terms of the Lesser GNU Public License. It is written in Java, and can be run with any virtual machine compatible with Sun's JDK 1.4. It can analyze programs written for any version of Java. FindBugs was originally developed by Bill Pugh. It is maintained by Bill Pugh, David Hovemeyer, and a team of volunteers.
FindBugs uses BCEL to analyze Java bytecode. It uses dom4j for XML manipulation. ~ Source :http://mojo.codehaus.org/findbugs-maven-plugin/
FindBugs Configuration Steps:
1) Setup Proxy: (Windows >> Preferences)
1) Setup Proxy: (Windows >> Preferences)
Example:HTTP proxy: 172.10.8.4 Port: 80
2) Help>>Software Updates>> Find and Install
3) Select “Search for new features to install”
4) Click on “New Remote Site…”
5) Name: Find Bugs URL: http://findbugs.cs.umd.edu/eclipse
6) Select FindBugs features
7) Accept the license and “Finish”. Eclipse will show the features to be downloaded and after “Next” it will show downloaded features with versions8) After completing installation, right click on any project in project explorer. A new menu “Find Bugs” should appear.
9) Windows >> Show View >> Others will show below View list with “FindBugs”. Select Bug Explorer.
10) Bug Explorer would show possible defects as shown below. “Bug details” will provide detailed information.
To configure with maven : http://mojo.codehaus.org/findbugs-maven-plugin/
0 comments:
Post a Comment