apache / tomee-site-ngSource Code Overview

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

Source Code Analysis Scope

Files includes and excluded from analyses

gsp

txt

properties

11 extensions are included in analyses: adoc, gsp, js, css, java, svg, gitignore, txt, xml, json, properties
10 criteria are used to exclude files from analysis:

exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (1 file).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (1 file).
exclude files with path like ".*/git[-]history[.]txt" (Git history) (1 file).
exclude files with path like ".*/git[-][a-zA-Z0-9_]+[.]txt" (Git data exports for sokrates analyses) (0 files).
exclude files with path like ".*/bootstrap[.](js|css|less|scss|styl)" (Bootstrap) (1 file).
exclude files with path like ".*/animate[.](css|less|scss|styl)" (Animate css) (1 file).
exclude files with path like ".*/normalize[.](css|less|scss|styl)" (Normalize css) (1 file).
exclude files with path like ".*[.]min[.]js" (Minimized JS library) (1 file).
exclude files with path like "(?i).*/jquery.*[.]js" (jQuery files) (1 file).
exclude files with path like ".*jquery[.].*[.]js" (jQuery library) (0 files).

The source code folder contains 229 files:

206 files are included in analyses.
23 files are excluded from analyses:

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.

73 files

1 file

132 files

Main Code

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

gsp

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

73 files match defined criteria (10,748 LOC, 100.0% vs. main code):

44 *.adoc files (4,003 LOC)
5 *.js files (3,656 LOC)
4 *.css files (1,374 LOC)
7 *.java files (1,109 LOC)
13 *.gsp files (606 LOC)

" *.adoc" is biggest, containing 37.24% of LOC.
" *.gsp" is smallest, containing 5.64% 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 ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".

1 file matches defined criteria (122 LOC, 1.1% vs. main code). All matches are in *.xml files.

Other Code

properties

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]json".
files with paths like ".*/README[.][a-z0-9]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*[.]txt".
files with paths like ".*[.]properties".
files with paths like ".*/[Ee]xamples/.*".

132 files match defined criteria (21,215 LOC, 197.4% vs. main code):

131 *.adoc files (21,198 LOC)
1 *.properties files (17 LOC)

" *.adoc" is biggest, containing 99.92% of LOC.
" *.properties" is smallest, containing 0.08% of LOC.

Analyzers

Info about analyzers used for source code examinations.

*.adoc files are analyzed with DefaultLanguageAnalyzer:

All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)

Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)

No unit size analysis

No conditional complexity analysis

No dependency analysis

*.js files are analyzed with JavaScriptAnalyzer:

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

No dependency analysis

*.css files are analyzed with CssAnalyzer:

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

*.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)

*.gsp files are analyzed with JspAnalyzer:

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

2023-08-10 18:21