1167
|
1 |
.. -*- coding: utf-8; -*-
|
|
2 |
|
|
3 |
================
|
|
4 |
Code analysis.
|
|
5 |
================
|
|
6 |
.. contemts::
|
|
7 |
|
|
8 |
About.
|
|
9 |
======
|
|
10 |
|
|
11 |
* http://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis
|
|
12 |
|
|
13 |
PMD.
|
|
14 |
====
|
|
15 |
|
|
16 |
PMD is a static ruleset based Java source code analyzer that identifies
|
|
17 |
potential problems.
|
|
18 |
|
|
19 |
PMD has plugins for JDeveloper, Eclipse, JEdit, JBuilder, Omnicore's CodeGuide,
|
|
20 |
NetBeans/Sun Studio, IntelliJ IDEA, TextPad, Maven, Ant, Gel, JCreator, Hudson,
|
|
21 |
Jenkins, Sonar and Emacs.
|
|
22 |
|
|
23 |
http://pmd.sf.net/
|
|
24 |
Home page.
|
|
25 |
http://en.wikipedia.org/wiki/PMD_%28software%29
|
1168
|
26 |
Wikipedia page.
|
|
27 |
|
|
28 |
Yasca.
|
|
29 |
======
|
|
30 |
|
|
31 |
Yasca leverages external open source programs, such as FindBugs, PMD, JLint,
|
|
32 |
JavaScript Lint, PHPLint, Cppcheck, ClamAV, Pixy, and RATS to scan specific file
|
|
33 |
types, and also contains many custom scanners developed for Yasca.
|
|
34 |
|
|
35 |
http://yasca.org/
|
|
36 |
Home page.
|
|
37 |
http://yasca.org/
|
|
38 |
Development home page.
|
|
39 |
http://en.wikipedia.org/wiki/Yasca
|
|
40 |
Wikipedia page.
|
|
41 |
|
1169
|
42 |
Sonar.
|
|
43 |
======
|
|
44 |
|
|
45 |
Sonar uses various static code analysis tools such as Checkstyle, PMD, FindBugs,
|
|
46 |
Clover to extract software metrics.
|
|
47 |
|
|
48 |
http://en.wikipedia.org/wiki/Sonar_%28software_quality%29
|
|
49 |
Wikipedia page. |