This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)(Learn how and when to remove this template message)
8.17 / April 30, 2018
|Type||Static code analysis|
|License||Lesser GNU General Public License|
Originally developed by Oliver Burn back in 2001, the project is maintained by a team of developers from around the world.
Advantages and limits
The programming style adopted by a software development project can help to ensure that the code complies with good programming practices which improves the quality, readability, re-usability of the code and may reduce the cost of development. The checks performed by Checkstyle are mainly limited to the presentation of the code. These checks do not confirm the correctness or completeness of the code.
Examples of available modules
Checkstyle defines a set of available modules, each of which provides rules checking with a configurable level of strictness (mandatory, optional...). Each rule can raise notifications, warnings, and errors. For example, Checkstyle can examine the following:
- Javadoc comments for classes, attributes and methods;
- Naming conventions of attributes and methods;
- The number of function parameters;
- Line lengths;
- The presence of mandatory headers;
- The use of imports, and scope modifiers;
- The spaces between some characters;
- The practices of class construction;
- Multiple complexity measurements.
- List of tools for static code analysis
- EclipseCS - Eclipse plugin for checkstyle.
- Checkstyle-IDEA - Checkstyle plugin for IntelliJ IDEA and Android Studio
- SevNTU-Checkstyle - extension for EclipseCS with number of check that are not part of checkstyle upstream.
- Checkstyle Addons - Additional Checkstyle checks
- Checkstyle for PHP - a PHP version of Checkstyle
|This software-engineering-related article is a stub. You can help Wikipedia by expanding it.|