Dashboards
Projects
Recent Projects
All Projects
Measures
Issues
Rules
Quality Profiles
Quality Gates
Log in
CTPath
src/main/java/org/opentripplanner/routing/alertpatch
Dashboard
Issues
Time Machine
Tools
Components
Issues Drilldown
Design
Libraries
src/main/java/org/opentripplanner/routing/alertpatch
[
hide
]
[
hide
]
[
hide
]
Time changes...
Δ since previous analysis (19 Oct 2015)
Δ over 30 days (14 Oct 2015)
Severity
Blocker
0
Critical
0
Major
27
Minor
5
Info
0
Rule
Local variables should not shadow class fields
8
Branches should have sufficient coverage by unit tests
4
Methods should not be too complex
4
Declarations should use Java collection interfaces such as "List" rather than specific implementation classes such as "LinkedList"
3
Source files should not have any duplicated blocks
1
Constant names should comply with a naming convention
1
Collapsible "if" statements should be merged
1
Expressions should not be too complex
1
Strings literals should be placed on the left side when checking for equality
1
"FIXME" tags should be handled
1
Method parameters, caught exceptions and foreach variables should not be reassigned
1
Useless parentheses around expressions should be removed to prevent any misunderstanding
1
The members of an interface declaration or class should appear in a pre-defined order
2
Control flow statements "if", "for", "while", "switch" and "try" should not be nested too deeply
2
Tabulation characters should not be used
1
AlertPatch.java
3
Alert.java
1