Tomcat
Source Code Overview

Source Code Analysis Scope
Files includes and excluded from analyses
  • 1 extension is included in analyses: java
  • 4 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/bin/.*" (0 files).
    • exclude files with path like ".*/docs/.*" (Documentation) (1 file).
    • exclude files with path like ".*/target/.*" (Compiled files) (0 files).
    • exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (0 files).
Overview of Analyzed Files
Basic stats on analyzed files
Intro
For analysis purposes we separate files in scope into several categories: main, test, generated, deployment and build, and other.

  • The main category contains all manually created source code files that are being used in the production.
  • Files in the main category are used as input for other analyses: logical decomposition, concerns, duplication, file size, unit size, and conditional complexity.
  • Test source code files are used only for testing of the product. These files are normally not deployed to production.
  • Build and deployment source code files are used to configure or support build and deployment process.
  • Generated source code files are automatically generated files that have not been manually changed after generation.
  • While a source code folder may contain a number of files, we are primarily interested in the source code files that are being written and maintained by developers.
  • Files containing binaries, documentation, or third-party libraries, for instance, are excluded from analysis. The exception are third-party libraries that have been changed by developers.

main249951 LOC (73%) 1771 files
test83628 LOC (24%) 635 files
other4556 LOC (1%) 77 files
build and deployment1607 LOC (<1%) 7 files
generated0 LOC (0%) 0 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 1771 files match defined criteria (249,951 lines of code, 100.0% vs. main code). All matches are in *.java files.


*.java249951 LOC (100%) 1771 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
  • The following criteria are used to filter files:
    • files with paths like ".*/test/.*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*[-]test[-].*".
  • 635 files match defined criteria (83,628 lines of code, 33.5% vs. main code). All matches are in *.java files.


*.java83628 LOC (100%) 635 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
  • The following criteria are used to filter files:
    • files with paths like ".*/deploy/.*".
    • files with paths like ".*/build[.]xml".
    • files with paths like ".*/pom[.]xml".
  • 7 files match defined criteria (1,607 lines of code, 0.6% vs. main code). All matches are in *.java files.


*.java1607 LOC (100%) 7 files
Other Code
  • The following criteria are used to filter files:
    • files with paths like ".*/(webapps|examples|res)/.*".
    • files with paths like ".*/(maven|findbugs)/.*".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/checkstyle[.]xml".
    • files with paths like ".*[.]properties".
  • 77 files match defined criteria (4,556 lines of code, 1.8% vs. main code). All matches are in *.java files.


*.java4556 LOC (100%) 77 files
Analyzers
Info about analyzers used for source code examinations.
  • *.java files are analyzed with JavaAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis (based on package names)

2020-09-11 18:07