PMD Results
The following document contains the results of PMD 5.0.5.
Files
org/apache/maven/plugin/surefire/AbstractSurefireMojo.java
Violation |
Line |
Unnecessary use of fully qualified name 'org.apache.maven.plugin.logging.Log' due to existing import 'org.apache.maven.plugin.logging.Log' |
948 |
Avoid empty catch blocks |
1832–1834 |
These nested if statements could be combined |
2227–2230 |
org/apache/maven/plugin/surefire/SurefireDependencyResolver.java
Violation |
Line |
Unnecessary use of fully qualified name 'org.apache.maven.plugin.logging.Log' due to existing import 'org.apache.maven.plugin.logging.Log' |
59 |
org/apache/maven/plugin/surefire/report/ConsoleOutputFileReporter.java
Violation |
Line |
Avoid empty catch blocks |
73–75 |
org/apache/maven/plugin/surefire/report/StatelessXmlReporter.java
Violation |
Line |
Unnecessary use of fully qualified name 'org.apache.maven.shared.utils.xml.XMLWriter' due to existing import 'org.apache.maven.shared.utils.xml.XMLWriter' |
127 |
Avoid unused method parameters such as 'fw'. |
496 |
Avoid unused private fields such as 'CDATA_ESCAPE_STRING_BYTES'. |
685 |
Avoid unused private fields such as 'AMP_BYTES'. |
687 |
org/apache/maven/plugin/surefire/util/DependencyScanner.java
Violation |
Line |
These nested if statements could be combined |
94–117 |
org/apache/maven/plugins/surefire/report/TestSuiteXmlParser.java
Violation |
Line |
These nested if statements could be combined |
104–107 |