| 1 |
Source: codenarc |
| 2 |
Maintainer: Debian Java Maintainers <[email protected]> |
| 3 |
Uploaders: Damien Raude-Morvan <[email protected]> |
| 4 |
Section: java |
| 5 |
Priority: optional |
| 6 |
Build-Depends: ant, |
| 7 |
debhelper-compat (= 13), |
| 8 |
default-jdk, |
| 9 |
default-jdk-doc, |
| 10 |
groovy, |
| 11 |
javahelper, |
| 12 |
junit4, |
| 13 |
libgmetrics-groovy-java, |
| 14 |
liblog4j1.2-java, |
| 15 |
maven-repo-helper |
| 16 |
Standards-Version: 4.7.0 |
| 17 |
Vcs-Browser: https://salsa.debian.org/java-team/codenarc |
| 18 |
Vcs-Git: https://salsa.debian.org/java-team/codenarc.git |
| 19 |
Homepage: https://github.com/CodeNarc/CodeNarc |
| 20 |
|
| 21 |
Package: libcodenarc-groovy-java |
| 22 |
Architecture: all |
| 23 |
Depends: ant, |
| 24 |
groovy, |
| 25 |
libgmetrics-groovy-java, |
| 26 |
liblog4j1.2-java, |
| 27 |
${misc:Depends} |
| 28 |
Suggests: libcodenarc-groovy-java-doc |
| 29 |
Description: Groovy library that provides static analysis features for Groovy code |
| 30 |
CodeNarc is a static analysis tool for Groovy source code, |
| 31 |
enabling monitoring and enforcement of many coding standards |
| 32 |
and best practices. CodeNarc applies a set of Rules |
| 33 |
(predefined and/or custom) that are applied to each Groovy |
| 34 |
file, and generates an HTML report of the results, including |
| 35 |
a list of rules violated for each source file, and a count |
| 36 |
of the number of violations per package and for the whole |
| 37 |
project. |
| 38 |
. |
| 39 |
CodeNarc is similar to popular static analysis tools such as |
| 40 |
PMD or Checkstyle, but is targeted at Groovy source code |
| 41 |
instead of Java. |
| 42 |
|
| 43 |
Package: libcodenarc-groovy-java-doc |
| 44 |
Architecture: all |
| 45 |
Section: doc |
| 46 |
Depends: ${misc:Depends} |
| 47 |
Recommends: libcodenarc-groovy-java |
| 48 |
Suggests: default-jdk-doc |
| 49 |
Description: Documentation for libcodenarc-groovy-java |
| 50 |
Documentation for CodeNarc that is a static analysis tool |
| 51 |
for Groovy source code, enabling monitoring and enforcement |
| 52 |
of many coding standards and best practices. CodeNarc applies |
| 53 |
a set of Rules (predefined and/or custom) that are applied |
| 54 |
to each Groovy file, and generates an HTML report of the |
| 55 |
results, including a list of rules violated for each source |
| 56 |
file, and a count of the number of violations per package |
| 57 |
and for the whole project. |
| 58 |
. |
| 59 |
CodeNarc is similar to popular static analysis tools such as |
| 60 |
PMD or Checkstyle, but is targeted at Groovy source code |
| 61 |
instead of Java. |