Using Codeanalyzer to analyze code metrics

My team has popularized the use of Codeanalyzer to analyze Code metrics (metric), sharing experience here.

The first explanation is that Codeanalyzer is a jar file that you can run, and it can be used to get statistics on our code, and here is a detailed explanation of how to use the tool in conjunction with our development environment.

(1) Copy the Code-analyzer-<version>.jar file to our Linux box (for example, the/home/cwang58/software directory)

(2) The configuration X-window is as follows, in particular, the input in the command should be Java-jar <your Path>/codeanalyzer-<version>.jar, as we have mentioned earlier, This tool is a self running jar package.

So the command we entered here is Java-jar/home/cwang58/software/codeanalyzer-0.7.0.jar.

(3) Start X-window, we can get the GUI of Codeanalyzer.

(4) We create a code set called "Pangaea Portal Codebase", you can also play any other meaningful name, it is only used to represent a collection of code, and then we use the JFileChooser component to point to our Code branch, It's going to go to the file system on our Linuxbox, of course you can. This code collection points to a specified item, such as/app/pangaea/portal/dbaasmetadataadmin.