- Check the eclipse problem view
- Group the problems: Use the menu "Group By/Type" in the Problems View
- Double click on a problem to find problem in code
Limitations
The problems found by UCDetector, are only suggestions.
Before deleting or changing your code you should really know what you are doing!
If UCDetector tells you, that there are no references of your class, method or field
your code still may be used by:
- Reflection
- Declaration in no java files like property files, xml files...
- Third party code, which is using your code
- Jars in your workspace
- To be continued...
Change visibility to private or protected may have side effects to inheritance,
reflection...
It is a good idea to do a full text search in your whole workspace,
for the piece of code you want to change.
Change your code
After checking carefully all the limitations above, maybe you decide to change
your code:
- Delete code, when UCDetector tells you that there are no references
- Move your code, when UCDetector tells you that there is only
1 reference (change "Limit" to 1 in "Window/Preferences")
- Change visibility to protected or private
Ignore code
/**
* Class is only used by reflection.
* Write a "NO_UCD" comment at the end of the line which should be ignored by UCDector.
*/
public class Example { // NO_UCD
 Clean markers
Delete UCDetector markers by right clicking on a java element which contains
the markers and select:
"UCDetector/Clean markers"
|
|
Check results
Run UCDetector
Count code checked by UCDetector
Detect class cycles