Résultats PMD
Le document suivant contient les résultats de PMD 5.3.5.
Fichiers
fr/paris/lutece/plugins/archive/business/ArchiveItemDAO.java
Violation |
Ligne |
Use block level rather than method level synchronization |
116–133 |
fr/paris/lutece/plugins/archive/service/archive/ArchivePlugin.java
Violation |
Ligne |
Document empty method |
50–51 |
fr/paris/lutece/plugins/archive/service/archive/ArchiveService.java
Violation |
Ligne |
Document empty constructor |
60–62 |
Avoid unnecessary constructors - the compiler will generate these for you |
60–62 |
Rather than using a lot of String arguments, consider using a container object for those values. |
81–82 |
Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block |
133 |
Avoid catching generic exceptions such as NullPointerException, RuntimeException, Exception in try-catch block |
180 |
fr/paris/lutece/plugins/archive/service/archive/DaemonArchive.java
Violation |
Ligne |
Overridable method 'init' called during object construction |
57 |
fr/paris/lutece/plugins/archive/service/archive/IArchiveService.java
Violation |
Ligne |
Rather than using a lot of String arguments, consider using a container object for those values. |
52–53 |
fr/paris/lutece/plugins/archive/util/ArchiveUtil.java
Violation |
Ligne |
A method/constructor shouldnt explicitly throw java.lang.Exception |
61 |
A method/constructor shouldnt explicitly throw java.lang.Exception |
61 |
StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. |
86 |
StringBuffer (or StringBuilder).append is called consecutively without reusing the target variable. |
87 |
A method/constructor shouldnt explicitly throw java.lang.Exception |
99 |
A method/constructor shouldnt explicitly throw java.lang.Exception |
99 |
fr/paris/lutece/plugins/archive/util/DoDownloadArchive.java
Violation |
Ligne |
Avoid variables with short names like os |
98 |
Deeply nested if..then statements are hard to read |
121–124 |