Violation |
Line |
Unnecessary use of fully qualified name 'org.apache.log4j.Logger.getLogger' due to existing import 'org.apache.log4j.Logger' |
112 |
The Logger variable declaration does not contain the static and final modifiers |
112 |
Use explicit scoping instead of the default package private level |
125–134 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
128 |
Use explicit scoping instead of the default package private level |
141–148 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
144 |
Use explicit scoping instead of the default package private level |
155–161 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
157 |
Use explicit scoping instead of the default package private level |
168–185 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
170 |
Use explicit scoping instead of the default package private level |
192–198 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
194 |
Use explicit scoping instead of the default package private level |
200–228 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
203 |
The String literal " - " appears 14 times in this file; the first occurrence is on line 218 |
218 |
Use explicit scoping instead of the default package private level |
236–254 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
238 |
Use explicit scoping instead of the default package private level |
263–282 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
265 |
Use explicit scoping instead of the default package private level |
293–313 |
Rather than using a lot of String arguments, consider using a container object for those values. |
293 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
295 |
Use explicit scoping instead of the default package private level |
321–339 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
323 |
Use explicit scoping instead of the default package private level |
347–365 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
349 |
Use explicit scoping instead of the default package private level |
372–397 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
374 |
Avoid variables with short names like jo |
384 |
The String literal "Account Shadow API call : mail=" appears 4 times in this file; the first occurrence is on line 389 |
389 |
Use explicit scoping instead of the default package private level |
405–432 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
407 |
Avoid variables with short names like jo |
419 |
Rather than using a lot of String arguments, consider using a container object for those values. |
440 |
Use explicit scoping instead of the default package private level |
440–471 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
442 |
Avoid variables with short names like jo |
452 |
Use explicit scoping instead of the default package private level |
479–518 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
481 |
Avoid variables with short names like jo |
490 |
Use explicit scoping instead of the default package private level |
527–564 |
If you run in Java5 or newer and have concurrent access, you should use the ConcurrentHashMap implementation |
529 |
Avoid variables with short names like jo |
539 |