What code analysis tools do you use for your Java projects? [closed]

Answer 1

in our project we use Sonar in front of checkstyle, pmd.... together with the CI (Bamboo, Hudson) we get also a nice history of our source quality and what directing we go. I do like Sonar, because you one central tool in the CI Stack that does it for you, and you can easy customize the rules for each project.

Answer 2

Checkstyle is another one I've used at a previous company... it's mainly for style checking, but it can do some static analysis too. Also, Clover for code coverage, though be aware it is not a free tool.

Answer 3

We use FindBugs and JDepend integrated with Ant. We use JUnit but we're not using any coverage tool.

I'm not using it integrated to Rational Application Developer (the IDE I'm using to develop J2EE applications) because I like how neat it looks when you run javac in the Windows console. :P

Answer 4

Structure 101 is good at code analysis and finding the cyclic package dependencies.

Answer 5

We are using FindBugs and Checkstyle as well as Clover for Code Coverage.

I think it's important to have some kind of static analysis, supporting your development. Unfortunately it's still not widely spread that these tools are important.

Answer 6

All of the following we use and integrate easiy in both our Maven 2.x builds and Eclipse/RAD 7:

• Testing - JUnit/TestNG
• Code analysis - FindBugs, PMD
• Code coverage - Clover

In addition, in our Maven builds we have:

• JDepend
• Tag checker (TODO, FIXME, etc)

Furthermore, if you're using Maven 2.x, CodeHaus has a collection of handy Maven plugins in their Mojo project.

Note: Clover has out-of-the-box integration with the Bamboo CI server (since they're both Atlassian products). There are also Bamboo plugins for FindBugs, PMD, and CheckStyle but, as noted, the free Hudson CI server has those too.