apache / shardingsphere-elasticjob - Source Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope

Files includes and excluded from analyses

properties

txt

xsd

cmd

17 extensions are included in analyses: java, md, xml, html, css, js, json, properties, yaml, svg, toml, sh, bat, txt, xsd, gitignore, cmd
7 criteria are used to exclude files from analysis:

exclude files with path like ".*/bin/.*" (Binaries for distribution) (3 files).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (6 files).
exclude files with path like ".*/mvnw\.cmd" (Maven) (1 file).
exclude files with path like ".*/docs/.*" (Documentation) (250 files).
exclude files with path like ".*/docs?/_?(build|themes?|templates?|static)/.*" (Sphinx) (0 files).
exclude files with path like "(?i).*/jquery.*[.]js" (jQuery files) (0 files).
exclude files with path like ".*jquery[.].*[.]js" (jQuery library) (0 files).

The source code folder contains 1,091 files:

676 files are included in analyses.
415 files are excluded from analyses:

Explore all 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.

Main Code

All manually created or maintained source code that defines logic of the product that is run in a production environment.

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

276 files match defined criteria (9,423 LOC, 100.0% vs. main code):

274 *.java files (9,338 LOC)
2 *.xml files (85 LOC)

" *.java" is biggest, containing 99.1% of LOC.
" *.xml" is smallest, containing 0.9% of LOC.

Test Code

Used only for testing of the product. Normally not deployed in a production environment.

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/[Tt]est/.*".
files with paths like ".*/test[.].*".
files with paths like ".*/e2e/.*".

302 files match defined criteria (12,916 LOC, 137.1% vs. main code):

260 *.java files (12,013 LOC)
39 *.xml files (884 LOC)
1 *.bat files (17 LOC)
2 *.sh files (2 LOC)

" *.java" is biggest, containing 93.01% of LOC.
" *.sh" is smallest, containing 0.02% of LOC.

Build and Deployment Code

Source code used to configure or support build and deployment process.

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/pom[.]xml".
files with paths like ".*[.]sh".
files with paths like ".*[.]bat".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".

30 files match defined criteria (1,832 LOC, 19.4% vs. main code). All matches are in *.xml files.

Other Code

properties

xsd

txt

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/[Ee]xamples/.*".
files with paths like ".*[.]md".
files with paths like ".*/README[.][a-z0-9]+".
files with paths like ".*[.]properties".
files with paths like ".*[.]txt".
files with paths like ".*/checkstyle[.]xml".
files with paths like ".*/checkstyle.*".
files with paths like ".*/[.]gitignore".
files with paths like ".*/resources/.*[.]xsd".
files with paths like ".*[.]json".
files with paths like ".*[.]svg".
files with paths like ".*/LICENSE[.][a-z0-9]+".

68 files match defined criteria (2,807 LOC, 29.8% vs. main code):

11 *.xml files (771 LOC)
6 *.md files (585 LOC)
20 *.java files (558 LOC)
13 *.properties files (424 LOC)
12 *.json files (330 LOC)
1 *.xsd files (87 LOC)
2 *.bat files (34 LOC)
1 *.txt files (16 LOC)
2 *.sh files (2 LOC)

" *.xml" is biggest, containing 27.47% of LOC.
" *.sh" is smallest, containing 0.07% of LOC.

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)

*.xml files are analyzed with XmlAnalyzer:

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)

No unit size analysis

No conditional complexity analysis

No dependency analysis

2025-05-07 15:54