CodeNarc analyzes Groovy code for defects, bad practices, inconsistencies, style issues and more. A flexible framework for rules, rulesets and custom rules means it’s easy to configure CodeNarc to fit into your project. Build tool, framework support, and report generation are all enterprise ready.
CodeNarc RulesCodeNarc triggers violations based on rules. Click the links to the left to view the index of all rules, or individual rule categories (rulesets), such as the basic, or import rules. Or you can create your own ruleset; see how easy it is in this screencast. |
|
Running CodeNarcRun CodeNarc with the Ant Task, the command-line runner, Docker, or as part of your test suite. Also, plugins exist for Maven, Gradle, Grails, Griffon, SonarQube, Visual Studio Code, and Jenkins. See our Integration page for more details. Reports come in HTML, XML, or text format. Take a look at a Sample CodeNarc HTML Report, or a Sample CodeNarc XML Report. |
RequirementsCodeNarc requires: |
Get it from Maven2For projects built using Maven, CodeNarc is available from the Maven Central Repository
|
InspirationsWe're inspired by the wonderful PMD and Checkstyle Java static analysis tools, as well as the extensive Groovy inspections performed by IntelliJ IDEA. |