Skip to main content

Find Bugs Plugin

Findbugs provides for a quick method of doing static code analysis. It can operate in a stand alone mode and integrates well with eclipse as well. More information on this can be found at
http://findbugs.sourceforge.net/

The installation comes with a number of built-in detectors. Additional detectors can be found at
http://fb-contrib.sourceforge.net/

While these detectors are useful, the real power of FB can be unlocked by writing a custom detector for you code. Below is a step by step tutorial that you can refer to for writing a custom detector for your code.
https://code.google.com/p/findbugs/wiki/DetectorPluginTutorial
http://www.ibm.com/developerworks/library/j-findbug2/

To write your own detectors you would need to know the byte code being generated for your classes and then based on those patterns write a detector which will serve your purpose. One good plug-in to view the byte code for your classes is the Dr. Garbage Byte Code Visualizer. It is available as a eclipse plugin and is very useful during the development.
http://www.drgarbage.com/bytecode-visualizer/

Once you have developed your dectector, testing/debugging it can be easily done using the APIs here

Comments

Popular posts from this blog

Exception in AppMerge flows' progression - Unable to resolve deadlock in factory claims [WebLogic 12.1.1]

While deploying my EAR which included a WAR, I was getting the following errors. While searching on the net for possible solutions to the issue, came across a post which indicated that the following setting for the domain was the cause for the same. The setting needs to be deselected. I tried the below url for steps to disable the setting for the domain that I had already created. http://stackoverflow.com/questions/12219782/how-do-you-turn-off-sip-support-in-weblogic-server-12c But that did not help. I then created a new domain and ensured that the setting was unchecked. This resolved the issue.