static analysis

I also downloaded the static analyzer incubator project and would like to know how to set it up. I saw there was a Code Audit view but it's pretty barren. The Wiki wasn't too insightful either. Thanks

I had found the same problem and I created new work item for this issue:
https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.workitem.viewWorkItem&id=34253

If you have any idea how to use the static analysis tool please post some guidelines here (so far I was able to open the code Audit view, which is empty and doesn't have any actions available).

I also downloaded the static analyzer incubator project and would like to know how to set it up. I saw there was a Code Audit view but it's pretty barren. The Wiki wasn't too insightful either. Thanks

Did anyone manage to get this working recently?

Corville.

Sorry I missed the initial post.

The only documentation that has been written so far is:
https://jazz.net/learn/LearnItem.jsp?href=content/docs/static-analysis/build-server-setup.html
https://jazz.net/learn/LearnItem.jsp?href=content/docs/static-analysis/index.html

Feedback on this documentation is welcome.

Jerome

This was very helpful.

Here are my comments.

1) Allow configuration of where you put staticAnalysis file, at the root of the project may be undesired, perhaps in a \build directory. Or wherever in the users projects.

2) Can we eliminate or re-use some of the original values from
the original build.xml. Like the compile activity where the src.dir, and destination.dir?


Questions:

I've gotten the generation of the static analsis results. However they aren't showing up in the build editor after a run. It says Analysis contribution missing.

What needs to get done to fix this?

Can you also include your complete build.xml that would illustrate that?

Thanks,

Corville.

corville wrote:

This was very helpful.

Here are my comments.

1) Allow configuration of where you put staticAnalysis file, at the
root of the project may be undesired, perhaps in a \build directory.
Or wherever in the users projects.

2) Can we eliminate or re-use some of the original values from
the original build.xml. Like the compile activity where the src.dir,
and destination.dir?


Questions:

I've gotten the generation of the static analsis results. However they
aren't showing up in the build editor after a run. It says Analysis
contribution missing.

What needs to get done to fix this?

Can you also include your complete build.xml that would illustrate
that?

Thanks,

Corville.

Thanks for the feedback Corville. For 1) and 2), these are very good point.

Can you please enter 2 work items using https://jazz.net/bugs/bugs.jsp?

For the problem with the generation of static analysis results, I updated
the scripts in https://jazz.net/learn/LearnItem.jsp?href=content/docs/static-analysis/build-server-setup.html
so that they work with Beta2. Also note that the snippet to paste in the build.xml
is different, so please redo the build server setup.

Jerome

What are the latest supported versions of PMD, FindBugs, and ECJ?

I tried version 4.2 of PMD and the Results pane of the Code Audit view shows me the violations, but each one is "Line unknown". The line number are in the generated .xml file, so I assume the format changed and the M6a version of the plugin can no longer parse the line number correctly.

I also was unable to get pmd 4.2 to work. I tried successively older versions from sourceforge until I got to 3.9 in which the line numbers can be successfully linked by the Code Analysis view of RTC. Thought this might save someone else some testing time in the future. 3.9 is a 2006 version of PMD so hopefully they can update the static analysis client to be compatible with a more recent version in the near future. I tested with version 1.0.1.1 build M20090206-0330 of RTC and JazzStaticAnalysis-0.7.0.

What are the latest supported versions of PMD, FindBugs, and ECJ?

I tried version 4.2 of PMD and the Results pane of the Code Audit view shows me the violations, but each one is "Line unknown". The line number are in the generated .xml file, so I assume the format changed and the M6a version of the plugin can no longer parse the line number correctly.