The usage and limitation of the useless Code scanning tool UCDetector

What this article shares with you is about the usage and limitations of the useless code scanning tool UCDetector. The editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article.

Projects that deposit or take over development often encounter a pile of useless code, but a class search is quite time-consuming. Here is an introduction to an eclipse plug-in to scan unreferenced classes, methods, and constants.

The plug-in is called UCDetector and the introduction address is http://www.ucdetector.org/index.html

Eclipse update site is: http://ucdetector.sourceforge.net/update

How to use it is to right-click on the project (you can select multiple modules by shift) and select UCDetector- > Detect unnecessary code

After the scan is completed, the html report is generated in the ucdetector_reports folder of the eclipse installation directory, and you can view it.

Plug-in limitations: the following code references cannot be scanned by UCDetector and need to be judged manually:

1. Reflection

2. Configure injection method in xml similar to spring

3. Third party call

4. Call jar

These are the usage and limitations of the useless code scanning tool UCDetector. The editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.