MissingPackageDeclarationRuleViolationTestCase.java
Package:
Results
| Date | 2007/07/27 |
| Codebase | 139 |
| Reviews | 284 |
| DPMO | 739 |
| Sigma | 4.679 |
Metrics
| Name | Number | Min | Avg | Max | Total |
| Class complexity | 1 | 1.00 | 1.00 | 1.00 | 1.00 |
| Code length | 1 | 3.00 | 3.00 | 3.00 | 3.00 |
| File length | 1 | 0.00 | 0.00 | 0.00 | 0.00 |
| Operation complexity | 1 | 1.00 | 1.00 | 1.00 | 1.00 |
| Work order | 1 | 73.77 | 73.77 | 73.77 | 73.77 |
Violations
| # | Line | Column | Name | Severity | Description |
| 1 | 31 | 1 | ER-016 | 2 | Missing package declaration - encourage structuring and avoid namesapace conflicts by using packages |
| 2 | 31 | 1 | ER-023 | 3 | Packages should begin with [] |
| 3 | 32 | 9 | ER-049 | 2 | Logger must be final |
-
JavaDoc
-
MissingPackageDeclarationRuleViolationTestCase
1
23
24
26
31public class MissingPackageDeclarationRuleViolationTestCase {
32 private static org.apache.log4j.Logger logger =
33 org.apache.log4j.Logger.getRootLogger();
34
35 private static final int TEN_CONST = 10;
36
37
38 public int getTen() {
39 logger.debug(this);
40
41 return TEN_CONST;
42 }
43}
44
45
Hammurapi 3 Copyright © 2004 Hammurapi Group. All Rights Reserved.