Apache Kafka
Source Code Overview

Source Code Analysis Scope
Files includes and excluded from analyses
  • 2 extensions are included in analyses: java, scala
  • 1 criterion is used to exclude files from analysis:
    • exclude files with path like ".*/docs/.*" (Documentation) (1 file).
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.

test277047 LOC (56%) 1238 files
main212448 LOC (43%) 1964 files
generated0 LOC (0%) 0 files
build and deployment0 LOC (0%) 0 files
other0 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 ".*".
  • 1964 files match defined criteria (212,448 lines of code, 100.0% vs. main code):
    • 1,720 *.java files (166,195 lines of code)
    • 244 *.scala files (46,253 lines of code)
  • " *.java" is biggest, containing 78.23% of code.
  • " *.scala" is smallest, containing 21.77% of code.


*.java166195 LOC (78%) 1720 files
*.scala46253 LOC (21%) 244 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 ".*/tests/.*".
    • files with paths like ".*[-]tests[-].*".
    • files with paths like ".*/test_.*".
    • files with paths like ".*_test[.].*".
  • 1238 files match defined criteria (277,047 lines of code, 130.4% vs. main code):
    • 936 *.java files (200,949 lines of code)
    • 302 *.scala files (76,098 lines of code)
  • " *.java" is biggest, containing 72.53% of code.
  • " *.scala" is smallest, containing 27.47% of code.


*.java200949 LOC (72%) 936 files
*.scala76098 LOC (27%) 302 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)
  • *.scala files are analyzed with ScalaAnalyzer:
    • 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
    • Basic heuristic dependency analysis

2020-09-11 18:57