Public report — jxfw, published 20 Sep 2026.
Concrete security findings (which rule fired, in which file, on which line; CVE IDs, secret matches,
dependency versions) are REDACTED in this version; ask the repo owner for the full report.
Public
Codebase surveyMeasured under the Code Assurance Index · rubric rubric-2026.09.15 (frozen) · verify this surveyFiledcd_eaa8c1b582cd4e23916b9de3a7191245
Filed 25 September 2026, 05:09 UTC
Public
9 critical495 serious17 minor46 could not be resolved — could be critical — see Limitations
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
20 September 2026, 21:00 UTC
A measurement, not a certificate. The Code Assurance Index does not certify,
approve or guarantee this codebase; it records a reproducible number and the evidence it was computed from. The
standard is authored by Canine Development, who also build Watchdog — its only implementation today. That is said
here so the number is checked rather than believed.
Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸
508findings with an exact file:lineof 521 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
30/126dimensions across the health lenses95362 LoC — wide & deep
This system is an adequate but fragile asset. With an overall health score of 51%, it functions reliably today but carries significant risk that threatens long-term stability and security. The codebase is medium-sized, representing a substantial investment of approximately 0.9 person-years to rebuild, valued at roughly €130,000. While the architecture is robust and the domain modeling is excellent, the system’s weakest points lie in its operational security and maturity, creating a vulnerability profile that demands immediate attention before technical debt compounds further.
The most critical issue is security exposure. With a readiness score of only 40%, the system lacks essential safeguards to prevent vulnerabilities from reaching production. This is not merely a technical oversight but a business risk: without automated checks, every release carries the potential for security regressions that could lead to data breaches or compliance failures. The cost of inaction is high, as fixing issues post-deployment is exponentially more expensive and disruptive than catching them during development. Strengthening this layer is the highest-leverage action available, offering protection that pays for itself by preventing costly outages and remediation efforts.
A secondary concern is the velocity tax imposed by code quality. Although the code is well-structured, complexity and duplication in certain areas create a hidden drag on development speed. Each change in these weaker sections likely costs 4–8% more effort than in clean code, a tax that compounds as the team grows. This inefficiency slows down feature delivery and increases the likelihood of defects, effectively raising the cost of every enhancement. Addressing these quality issues yields immediate returns by freeing up engineering capacity for higher-value work.
The system’s strengths are notable: the architecture is sound, and the domain logic is clearly modeled, providing a solid foundation for future changes. However, the lack of measured test coverage and automated security gates leaves the team flying blind. To focus first, implement a static analysis security testing step in the continuous integration pipeline. This single action addresses the most critical risk with minimal effort, ensuring that security regressions are caught before they impact users. This step is the most effective way to stabilize the system and protect the investment already made.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
314 finding(s) are new versus the previous scan (2026-07-20) — surfaced by this scheduled scan itself, no pull request required. Showing the first 100; the full set is in the report.
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
0.7× (at 51% quality) — the last 20% of quality is most of the work
Size & shape
REDACTED · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~0.9 person-years of build effort (about ~€130,000 to rebuild). Its weakest lens is Security at 40% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain REDACTED (×1.4) — DDD/clean architecture, domain model × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2).
Resolve the 7 REDACTED finding(s) charged to Static Analysis (SAST) — the other 2 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
Value concentrated against a weak lens · REDACTED · Value at risk
This is a REDACTED asset (~0.9 person-years to rebuild), and its weakest lens is Security at 40%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Security first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · REDACTED · Leverage
Of everything flagged, the best return on effort is: Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
A velocity tax on every change · REDACTED · Economics
The code-quality signals (complexity, duplication, cohesion) average 6.5/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 4–8% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D1/D2/D4 code quality: averaging 6.5/10 across the code-quality signals actually measured
→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.
The top fix pays for itself · REDACTED · Economics
The top-ranked fix costs roughly 1–3 engineer-days once. Not doing it costs about 0.1–0.5 engineer-days every year, paid as drag on the ~819 lines this team changes annually — a bill that arrives whether or not anyone books it. On those figures the fix breaks even in roughly 27–479 months and is free after that. Method, stated so this is not read as a quotation: debt from the ranked task's effort band; interest = annual changed lines (measured, annualised from the 90-day window) ÷ an ASSUMED 150–400 lines per engineer-day × the 4–8% drag implied by the code-quality signals; breaking point = debt ÷ annual interest. A modelled planning range built from measured inputs and one named assumption — not a quotation, a valuation, or a certified figure.
Evidence: D15 churn: 202 line(s) changed over a 90-day window ⇒ ~819/year · D1/D2/D4 code quality: averaging 6.5/10 ⇒ a 4–8% drag on each change · top-ranked remediation: REDACTED effort ⇒ about 1–3 engineer-day(s)
→ Do the top-ranked fix now if this code will still be yours in 479 months.
Architecture — module dependency matrix
Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
226 modules, 460 dependencies. 9 dependency cycles across 39 modules, marked above the diagonal.
Showing the 40 most-connected modules; 186 more are not drawn.
Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
reporting.xslfo.layouts.formatters uses reporting.xslfo.layouts. Changing reporting.xslfo.layouts can break reporting.xslfo.layouts.formatters, not the reverse.
Position
Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.
8→23 reporting.xslfo.layouts.formatters depends on reporting.xslfo.implcycle✕
Type pairs
1 distinct (type in reporting.xslfo.layouts.formatters → type in reporting.xslfo.impl) reference.
reporting.xslfo.layouts.formatters uses reporting.xslfo.impl. Changing reporting.xslfo.impl can break reporting.xslfo.layouts.formatters, not the reverse.
Position
Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.
9→15 reporting.xslfo.renderer.excel.core.element.area depends on reporting.xslfo.renderer.core.commoncycle✕
Type pairs
4 distinct (type in reporting.xslfo.renderer.excel.core.element.area → type in reporting.xslfo.renderer.core.common) references.
reporting.xslfo.renderer.excel.core.element.area uses reporting.xslfo.renderer.core.common. Changing reporting.xslfo.renderer.core.common can break reporting.xslfo.renderer.excel.core.element.area, not the reverse.
Position
Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.
10→15 reporting.xslfo.renderer.word.processing.tree.element.root depends on reporting.xslfo.renderer.core.commoncycle✕
Type pairs
2 distinct (type in reporting.xslfo.renderer.word.processing.tree.element.root → type in reporting.xslfo.renderer.core.common) references.
reporting.xslfo.renderer.word.processing.tree.element.root uses reporting.xslfo.renderer.core.common. Changing reporting.xslfo.renderer.core.common can break reporting.xslfo.renderer.word.processing.tree.element.root, not the reverse.
Position
Above the diagonal — a cycle. Neither module can be changed, tested or deployed independently until one of these dependencies goes.
11→7 core.exception.exceptions depends on core.localization✕
Type pairs
8 distinct (type in core.exception.exceptions → type in core.localization) references.
reporting.xslfo.layouts uses reporting.xslfo.layouts.formatters. Changing reporting.xslfo.layouts.formatters can break reporting.xslfo.layouts, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
14→23 reporting.xslfo.layouts depends on reporting.xslfo.implcycle✕
Type pairs
2 distinct (type in reporting.xslfo.layouts → type in reporting.xslfo.impl) references.
reporting.xslfo.renderer.core.common uses reporting.xslfo.renderer.excel.core.element.area. Changing reporting.xslfo.renderer.excel.core.element.area can break reporting.xslfo.renderer.core.common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
15→10 reporting.xslfo.renderer.core.common depends on reporting.xslfo.renderer.word.processing.tree.element.root✕
Type pairs
1 distinct (type in reporting.xslfo.renderer.core.common → type in reporting.xslfo.renderer.word.processing.tree.element.root) reference.
reporting.xslfo.renderer.core.common uses reporting.xslfo.renderer.word.processing.tree.element.root. Changing reporting.xslfo.renderer.word.processing.tree.element.root can break reporting.xslfo.renderer.core.common, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
reporting.xslfo.renderer.excel.core.element.root uses reporting.xslfo.renderer.excel.core.element.area. Changing reporting.xslfo.renderer.excel.core.element.area can break reporting.xslfo.renderer.excel.core.element.root, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
17→15 reporting.xslfo.renderer.excel.core.element.root depends on reporting.xslfo.renderer.core.common✕
Type pairs
5 distinct (type in reporting.xslfo.renderer.excel.core.element.root → type in reporting.xslfo.renderer.core.common) references.
reporting.xslfo.renderer.excel.core.element.root uses reporting.xslfo.renderer.core.common. Changing reporting.xslfo.renderer.core.common can break reporting.xslfo.renderer.excel.core.element.root, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
18→1 reporting.xslfo.renderer.word.rendering depends on core.reporting✕
Type pairs
1 distinct (type in reporting.xslfo.renderer.word.rendering → type in core.reporting) reference.
reporting.xslfo.renderer.word.rendering uses core.reporting. Changing core.reporting can break reporting.xslfo.renderer.word.rendering, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
18→10 reporting.xslfo.renderer.word.rendering depends on reporting.xslfo.renderer.word.processing.tree.element.root✕
Type pairs
1 distinct (type in reporting.xslfo.renderer.word.rendering → type in reporting.xslfo.renderer.word.processing.tree.element.root) reference.
reporting.xslfo.renderer.word.rendering uses reporting.xslfo.renderer.word.processing.tree.element.root. Changing reporting.xslfo.renderer.word.processing.tree.element.root can break reporting.xslfo.renderer.word.rendering, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
18→15 reporting.xslfo.renderer.word.rendering depends on reporting.xslfo.renderer.core.common✕
Type pairs
1 distinct (type in reporting.xslfo.renderer.word.rendering → type in reporting.xslfo.renderer.core.common) reference.
reporting.xslfo.renderer.word.rendering uses reporting.xslfo.renderer.core.common. Changing reporting.xslfo.renderer.core.common can break reporting.xslfo.renderer.word.rendering, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
19→3 core.facade.webclient.impl depends on metamodel.runtime✕
Type pairs
2 distinct (type in core.facade.webclient.impl → type in metamodel.runtime) references.
reporting.xslfo.renderer.excel uses reporting.xslfo.renderer.core.common. Changing reporting.xslfo.renderer.core.common can break reporting.xslfo.renderer.excel, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
20→17 reporting.xslfo.renderer.excel depends on reporting.xslfo.renderer.excel.core.element.root✕
Type pairs
2 distinct (type in reporting.xslfo.renderer.excel → type in reporting.xslfo.renderer.excel.core.element.root) references.
reporting.xslfo.renderer.excel uses reporting.xslfo.renderer.excel.core.element.root. Changing reporting.xslfo.renderer.excel.core.element.root can break reporting.xslfo.renderer.excel, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
21→9 reporting.xslfo.renderer.excel.core.rendering.excel depends on reporting.xslfo.renderer.excel.core.element.area✕
Type pairs
2 distinct (type in reporting.xslfo.renderer.excel.core.rendering.excel → type in reporting.xslfo.renderer.excel.core.element.area) references.
reporting.xslfo.renderer.excel.core.rendering.excel uses reporting.xslfo.renderer.excel.core.element.area. Changing reporting.xslfo.renderer.excel.core.element.area can break reporting.xslfo.renderer.excel.core.rendering.excel, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
21→15 reporting.xslfo.renderer.excel.core.rendering.excel depends on reporting.xslfo.renderer.core.common✕
Type pairs
1 distinct (type in reporting.xslfo.renderer.excel.core.rendering.excel → type in reporting.xslfo.renderer.core.common) reference.
reporting.xslfo.renderer.excel.core.rendering.excel uses reporting.xslfo.renderer.core.common. Changing reporting.xslfo.renderer.core.common can break reporting.xslfo.renderer.excel.core.rendering.excel, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
21→17 reporting.xslfo.renderer.excel.core.rendering.excel depends on reporting.xslfo.renderer.excel.core.element.root✕
Type pairs
2 distinct (type in reporting.xslfo.renderer.excel.core.rendering.excel → type in reporting.xslfo.renderer.excel.core.element.root) references.
reporting.xslfo.renderer.excel.core.rendering.excel uses reporting.xslfo.renderer.excel.core.element.root. Changing reporting.xslfo.renderer.excel.core.element.root can break reporting.xslfo.renderer.excel.core.rendering.excel, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
22→4 core.facade.webclient depends on core.facade.webclient.file✕
Type pairs
2 distinct (type in core.facade.webclient → type in core.facade.webclient.file) references.
reporting.xslfo.impl uses reporting.xslfo.layouts.formatters. Changing reporting.xslfo.layouts.formatters can break reporting.xslfo.impl, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
23→14 reporting.xslfo.impl depends on reporting.xslfo.layouts✕
Type pairs
1 distinct (type in reporting.xslfo.impl → type in reporting.xslfo.layouts) reference.
transfer.component.imp.context.handler uses transfer.impl.imp.context.data. Changing transfer.impl.imp.context.data can break transfer.component.imp.context.handler, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
32→22 transfer.impl.exp depends on core.facade.webclient✕
Type pairs
2 distinct (type in transfer.impl.exp → type in core.facade.webclient) references.
transfer.component.imp.context uses transfer.impl.imp.context.data. Changing transfer.impl.imp.context.data can break transfer.component.imp.context, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
34→31 transfer.component.imp.context depends on transfer.component.imp.context.handler✕
Type pairs
1 distinct (type in transfer.component.imp.context → type in transfer.component.imp.context.handler) reference.
transfer.component.imp.context uses transfer.component.imp.context.handler. Changing transfer.component.imp.context.handler can break transfer.component.imp.context, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
transfer.impl.imp uses transfer.component.imp.context.handler. Changing transfer.component.imp.context.handler can break transfer.impl.imp, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
36→34 transfer.impl.imp depends on transfer.component.imp.context✕
Type pairs
7 distinct (type in transfer.impl.imp → type in transfer.component.imp.context) references.
transfer.component.imp uses transfer.component.imp.context.handler. Changing transfer.component.imp.context.handler can break transfer.component.imp, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
38→34 transfer.component.imp depends on transfer.component.imp.context✕
Type pairs
3 distinct (type in transfer.component.imp → type in transfer.component.imp.context) references.
transfer.impl.imp.context uses transfer.impl.imp.context.data. Changing transfer.impl.imp.context.data can break transfer.impl.imp.context, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→31 transfer.impl.imp.context depends on transfer.component.imp.context.handler✕
Type pairs
2 distinct (type in transfer.impl.imp.context → type in transfer.component.imp.context.handler) references.
transfer.impl.imp.context uses transfer.component.imp.context.handler. Changing transfer.component.imp.context.handler can break transfer.impl.imp.context, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→34 transfer.impl.imp.context depends on transfer.component.imp.context✕
Type pairs
14 distinct (type in transfer.impl.imp.context → type in transfer.component.imp.context) references.
transfer.impl.imp.context uses transfer.component.imp.context. Changing transfer.component.imp.context can break transfer.impl.imp.context, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
39→38 transfer.impl.imp.context depends on transfer.component.imp✕
Type pairs
3 distinct (type in transfer.impl.imp.context → type in transfer.component.imp) references.
transfer.config uses transfer.component.imp.context.handler. Changing transfer.component.imp.context.handler can break transfer.config, not the reverse.
Position
Below the diagonal — points down the layering, which is what you want.
40→34 transfer.config depends on transfer.component.imp.context✕
Type pairs
4 distinct (type in transfer.config → type in transfer.component.imp.context) references.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2021 — Injection
19
REDACTED / Critical
Roadmap
First, integrate automated security scanning into the CI pipeline to block builds containing vulnerabilities, and implement draft releases or approval gates to prevent faulty deployments from reaching users. Next, maintain a changelog for every release to track shipped changes and expand the README with clear getting-started instructions and an architecture overview. Finally, establish a structured repository for architecture decision records to document significant design choices and their consequences.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2).
Resolve the 7 REDACTED finding(s) charged to Static Analysis (SAST) — the other 2 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 9
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 495
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 17
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 46
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 27 of 30 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 30 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 508 of 521 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) and this repository declares a JVM test suite (repository root, Maven), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Dependency Hygiene ran out of its 5-minute budget before it had finished, so what it reports here is a floor rather than a complete count. The rows above are real and stand; what is not known is how many more there are. This is a limit of the analysis run, not a finding about this repository.
D14 License Compliance — evaluation did not complete — License Compliance not included (check did not complete) — excluded from the score.
D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Git history depth insufficient — this repository has 18 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 18 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: D22 has no public-API collector for any other ecosystem, and the remedy is to write one — no change to the scan image can close it.
D34 Knowledge Freshness — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Too few commits to judge knowledge freshness (18 commit(s) sampled).
D35 Change Coupling — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Git history depth insufficient — this repository has 18 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (go.mod, a Gemfile's ruby directive, a Dockerfile) is simply not read here yet.
AX3 Project dependency cycles — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over which project references which — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's reach — not a finding that the repository is free of what this check looks for.
AX4 Dependency direction — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the direction each project reference points — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's reach — not a finding that the repository is free of what this check looks for.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX8 Test isolation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over which projects are test projects, and what they reference — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's reach — not a finding that the repository is free of what this check looks for.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm one resolves each comparison operand to the domain member it judges, and that binding exists only in a Roslyn compilation, which this run did not load. Arm two ran over the neutral model because this repository's frontend declares whether each construction is produced or passed. A rule decided in two places would not appear above.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P1 CI/CD gates — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
47 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was AttributeParser.processProperties at 109. A further 9 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being XFWConstants.getUri at 30 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: jxfw-eclipse-bundles/bundles/jxfw-metamodel/src/main/java/ru/croc/ctp/jxfw/metamodel/XFWConstants.java (XFWConstants.getUri at 30), jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/core/common/HelpFuncs.java (HelpFuncs.getSizeInPointsEx at 16), jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/FoFont.java (FoFont.setFontWeight at 16), jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/facade/webclient/CriteriaComposer.java (CriteriaComposer.addCriteria at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 42 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 AttributeParser.processProperties (cyclomatic 109) finding(s) in Cyclomatic Complexity — start with AttributeParser.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TableLayout.writeTotalRow (cyclomatic 77) finding(s) in Cyclomatic Complexity — start with TableLayout.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 AttributeParser.processProperty (cyclomatic 77) finding(s) in Cyclomatic Complexity — start with AttributeParser.java. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 115 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 AttributeParser.processBorderAttribute (cognitive 27) finding(s) in Cognitive Complexity — start with AttributeParser.java (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 TableLayout.writeTotalRow (cognitive 366) finding(s) in Cognitive Complexity — start with TableLayout.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TableLayout.writeGroupBound (cognitive 200) finding(s) in Cognitive Complexity — start with TableLayout.java. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.9 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 12 TooManyMethods finding(s) in God Classes — start with ToServiceGenerator.java, TransferToServiceGenerator.java, LoggerOverReflection.java. — One of this dimension's main actionable groups (12 warning-level).
Resolve the 11 ClassTooLong finding(s) in God Classes — start with ToServiceGenerator.java, WordRenderer.java, TransferToServiceGenerator.java. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 11 FileTooLong finding(s) in God Classes — start with TableLayout.java, ToServiceGenerator.java, WordRenderer.java. — One of this dimension's main actionable groups (11 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
155 duplicated block group(s) detected. A further 6 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 55 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 15 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with TransferToServiceGenerator.java (4), WordRenderer.java (2), AbstractFacadeGenerator.java (2). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 11 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with TransferToServiceGenerator.java (3), ToServiceGenerator.java, AttributeParser.java. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 10 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with TransferToServiceGenerator.java (4), JsModelGenerator.java, TableLayout.java. — One of this dimension's main actionable groups (10 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
190 test methods: 190 unit, 0 integration, 0 BDD, 0 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality7.9 / 10Strong✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
3 skipped (3 with a documented reason), 27 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 190 tests.
No assertions: caseIgnoreAndCaseSensitiveOperators · ×27jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposerTest.java:278
Resolve the 27 No assertions finding(s) in Test Quality — start with PredicateComposerTest.java (12), TestCmfEnumUtil.java (2), XslfoReportProfileTest.java (2). — One of this dimension's main actionable groups (27 warning-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
84 deducted task-comment markers across 95362 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 69 TodoComment finding(s) in Explicit Debt — start with TestDomainObject.java (10), TestObject.java (9), XslFoProfileWriter.java (7). — One of this dimension's main actionable groups (69 warning-level).
Resolve the 15 FixmeComment finding(s) in Explicit Debt — start with EcoreGenerator.java (3), SelectComposer.java, CriteriaComposer.java. — One of this dimension's main actionable groups (15 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
jXFW is described in a single README with an external documentation link and installation notes for Maven; the body is thin on architecture/design docs and lacks any usage or contribution guidance. The project name 'jXFW' appears to be a placeholder (the README links to http://185.12.28.40/docsite/ which is not public), so it is unclear what the framework actually does.
Documentation: no usage examplesREADME.md
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged REDACTED. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
19 finding(s): 0 critical, 9 high, 8 medium, 2 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 REDACTED finding(s) charged to Static Analysis (SAST) — the other 2 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (9 issue-level, 7 of them charged here).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.
Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
The root README is 38 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
What to do
Expand the README with getting-started, architecture overview and a project map.
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 32 of 32 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree, with each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
What to do
Run the test suite in CI via an explicit runner step (`mvn test` for the toolchain this pipeline already uses) and gate merges on it.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1036 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 92 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not included — no .java test runner
D14 License Compliance — License Compliance not included (check did not complete)
D16 Bus Factor — single-contributor repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — Production source is present (.java) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — symbol resolution incomplete — navigability not assessed
D30 Dependency Vulnerabilities — osv: the scanner produced no output at all, so no dependency was actually scanned
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D34 Knowledge Freshness — too few commits to judge knowledge freshness
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — osv: the scanner produced no output at all, so no dependency was actually scanned
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a CS/VB/GO/SCALA/SWIFT/DART class graph, and this repository's production source is .java, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (3 event handler(s))
ED5 Idempotency — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — not assessed — schema-migration practice is read from a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
TodoComment jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:183— // TODO Создаем временную ссылку на объект, так как мы не знаем порядок — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/AbstractEcoreGenerator.java:117— // TODO Убрать, так как уже есть в {@link PersistenceModuleContext} — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/AbstractEcoreGenerator.java:151— // TODO Поддержать Lob — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/AbstractEcoreGenerator.java:245— //TODO: Однажды созданные enum дальше не обновляются. Сделать обновление — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/impl/DataSourceEcoreGenerator.java:157— // TODO JXFW-861: Установлена валидациия. В эту часть кода заходить не должны.
TodoComment jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposer.java:186— // TODO выяснить в каких случаях используется — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/facade/webclient/DomainToMapper.java:16— //TODO: все объекты в / из которых происходит преобразование, должны быть доменными <T extends DomainObject<?>> { — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/load/LoadServiceSupport.java:23— //TODO: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/load/impl/LoadServiceImpl.java:289— //TODO: надо разобраться с доменными сервисами и сервисами полнотекстового поиска, убрать эту спецфику в — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/store/impl/UnitOfWorkMultiStoreServiceImpl.java:75— //TODO перенести конвертация в фасад WebClient — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/domain/TestDomainObject.java:17— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/domain/TestDomainObject.java:23— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/domain/TestDomainObject.java:29— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/domain/TestDomainObject.java:35— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/domain/TestDomainObject.java:40— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/domain/TestDomainObject.java:45— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/domain/TestDomainObject.java:50— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/domain/TestDomainObject.java:56— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/domain/TestDomainObject.java:62— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/domain/TestDomainObject.java:68— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/services/TestObject.java:27— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/services/TestObject.java:48— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/services/TestObject.java:53— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/services/TestObject.java:59— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/services/TestObject.java:65— // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
No assertions: caseIgnoreAndCaseSensitiveOperators jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposerTest.java:278— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testContainsAndMultipleNotContainsOnOneField jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposerTest.java:75— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testMassiveInequalities jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposerTest.java:230— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testMultiMapOrderedStringOperatorsWithIgnoreCase jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposerTest.java:183— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testMultiMapOrderedStringOperatorsWithoutIgnoreCase jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposerTest.java:159— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testMultipleContainsAndMultipleNotContainsOnOneField jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposerTest.java:58— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testMultipleContainsAndNotContainsOnOneField jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposerTest.java:91— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testOp2 jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposerTest.java:52— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testOperatorAnyOfListWithNullOperator jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposerTest.java:123— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testOperatorValueIsNull jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposerTest.java:110— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testOperatorsOfComparing jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposerTest.java:135— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testOperatorsOfFlags jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposerTest.java:207— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: storeContextCreation jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/store/StoreContextTest.java:35— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testGetEnumValueFail jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/util/TestCmfEnumUtil.java:75— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testValueOfInvalidValue jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/util/TestCmfEnumUtil.java:63— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: beforeStoreFailTest jxfw-jpa-runtime/src/test/java/ru/croc/ctp/jxfw/jpa/store/impl/UnitOfWorkJpaStoreServiceImplTest.java:31— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: validateReportProfile jxfw-reporting-xsl-fo/src/test/java/ru/croc/ctp/jxfw/reporting/xslfo/impl/XslfoReportProfileTest.java:28— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: validateReportProfileAlien jxfw-reporting-xsl-fo/src/test/java/ru/croc/ctp/jxfw/reporting/xslfo/impl/XslfoReportProfileTest.java:11— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: throwExceptionIfAggregateFunctionIsUnknown jxfw-reporting-xsl-fo/src/test/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/LayoutTableTest.java:11— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: addSomeInfoToXmlTextReader jxfw-reporting-xsl-fo/src/test/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/core/common/XmlTextReaderTest.java:27— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: createXmlTextReader jxfw-reporting-xsl-fo/src/test/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/core/common/XmlTextReaderTest.java:19— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: rowHeightStrategyDefaultIsUsed jxfw-reporting-xsl-fo/src/test/java/ru/croc/ctp/jxfw/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/XslFo2ExcelRendererTest.java:37— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testFewNotResolveDependencies jxfw-transfer/src/test/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportDependencyManagerTest.java:54— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testFewNotResolveDependenciesWithNotLoadedDto jxfw-transfer/src/test/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportDependencyManagerTest.java:72— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: checkEcorePriorityEclipseCaseExpectException modelgen-maven-plugin/src/test/java/ru/croc/ctp/jxfw/mojo/modelgen/AggregateTest.java:219— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
FixmeComment jxfw-cass-runtime/src/main/java/ru/croc/ctp/jxfw/cass/facade/webclient/SelectComposer.java:205— //FIXME: predicateByID — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/facade/webclient/CriteriaComposer.java:472— //FIXME: predicateByID — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:314— //FIXME XfwValueType.UNDEFINED добавлен в JXFW-953, где затрагиваются только комплексные типы
FixmeComment jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:780— // fixme — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:837— // FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/facade/webclient/impl/WebclientQueryParamsBuilder.java:157— // FIXME JXFW-1215 что тут будет с комплексными ключами в CASS и SOLR?
FixmeComment jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/store/StoreResult.java:88— // FIXME JXFW-1223 сюда должен пойти контекст сохранения => контексты должны иметь общую иерархию
FixmeComment jxfw-eclipse-bundles/bundles/jxfw-metamodel/src/main/java/ru/croc/ctp/jxfw/metamodel/XFWConstants.java:158— //FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/solr/ToServiceGeneratorSolr.java:127— //FIXME — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment jxfw-export-poi/src/main/java/ru/croc/ctp/jxfw/export/poi/impl/views/ExcelView.java:133— // FIXME как лучше определить ширину страницы? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java:77— //FIXME: идентификатор не должен определяться по наименованию поля — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/jpa/ToServiceGeneratorJpa.java:82— //FIXME: идентификатор не должен определяться по наименованию поля — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:501— // FIXME: захардкожено — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (8 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1065— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1065-1072 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1153-1160 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1065` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) scriptgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/mojo/GenerateCqlScriptsMojo.java:118— scriptgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/mojo/GenerateCqlScriptsMojo.java:118-125 | scriptgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/mojo/GenerateSolrSchemaMojo.java:113-120 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/MasterDetailLayout.java:153— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/MasterDetailLayout.java:153-163 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/MasterDetailLayout.java:239-246 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/MasterDetailLayout.java:153` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java:426— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java:426-433 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/FoFont.java:371-378 — before extracting anything, compare `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java` and `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/FoFont.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java:426` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/logging/AreaLogHelper.java:99— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/logging/AreaLogHelper.java:99-106 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/logging/AreaLogHelper.java:130-137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/element/root/GenericArea.java:171— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/element/root/GenericArea.java:171-178 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/element/root/GenericArea.java:198-205 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/element/root/GenericArea.java:171` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:374— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:374-381 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:627-634 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:374` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `area` to `CharacterArea` in one and `InlineArea` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (8 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:909— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:909-916 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:979-986 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:909` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java:164— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java:164-171 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/jpa/ToServiceGeneratorJpa.java:176-183 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/jpa/ToServiceGeneratorJpa.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:818— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:818-825 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:886-893 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:895— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:895-902 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:975-982 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1081— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1081-1088 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1169-1176 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/AbstractFacadeGenerator.java:97— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/AbstractFacadeGenerator.java:97-104 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/FacadeGenerator.java:182-189 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/AbstractFacadeGenerator.java:111— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/AbstractFacadeGenerator.java:111-118 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/FacadeGenerator.java:173-180 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:960— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:960-968 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/TransientXfwObjectToGenerator.java:79-86 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `builder` to `Builder` in one and `MethodSpec.Builder` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
TooManyMethods: ToServiceGenerator wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:93— TooManyMethods — 83 methods. The bar is 30 methods; this is 53 over it, 2.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TransferToServiceGenerator jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:85— TooManyMethods — 72 methods. The bar is 30 methods; this is 42 over it, 2.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LoggerOverReflection jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/xtend/logging/impl/LoggerOverReflection.java:11— TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XslFoProfileWriter jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/XslFoProfileWriter.java:36— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XslfoTable jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/table/XslfoTable.java:24— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XMMEditor jxfw-eclipse-bundles/bundles/jxfw-metamodel.editor/src/ru/croc/ctp/jxfw/XtendMetaModel/presentation/XMMEditor.java:168— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LayoutColumn jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:55— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GenericArea jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/GenericArea.java:27— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: JsModelGenerator wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/JsModelGenerator.java:56— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WordRenderer jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:115— TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ObservableList jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/domain/impl/ObservableList.java:22— TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XfwClassImpl jxfw-eclipse-bundles/bundles/jxfw-metamodel/src/main/java/ru/croc/ctp/jxfw/metamodel/runtime/impl/XfwClassImpl.java:27— TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ToServiceGenerator wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:93— ClassTooLong — 1198 significant lines (blank, comment-only and punctuation-only lines excluded), 83 methods. The bar is 400 significant lines; this is 798 over it, 3.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WordRenderer jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:115— ClassTooLong — 1014 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 614 over it, 2.54× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TransferToServiceGenerator jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:85— ClassTooLong — 897 significant lines (blank, comment-only and punctuation-only lines excluded), 72 methods. The bar is 400 significant lines; this is 497 over it, 2.24× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: XMMEditor jxfw-eclipse-bundles/bundles/jxfw-metamodel.editor/src/ru/croc/ctp/jxfw/XtendMetaModel/presentation/XMMEditor.java:168— ClassTooLong — 699 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 299 over it, 1.75× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AreaTreeBuilder jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:101— ClassTooLong — 660 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 260 over it, 1.65× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EcoreGenerator jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:74— ClassTooLong — 535 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 135 over it, 1.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: GenericLayoutManager jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/layout/layoutmanager/GenericLayoutManager.java:34— ClassTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 101 over it, 1.25× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: XslFoProfileWriter jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/XslFoProfileWriter.java:36— ClassTooLong — 492 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 400 significant lines; this is 92 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WebClientControllerCreator wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:87— ClassTooLong — 469 significant lines (blank, comment-only and punctuation-only lines excluded), 18 methods. The bar is 400 significant lines; this is 69 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AttributeParser jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/attribute/AttributeParser.java:89— ClassTooLong — 428 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 28 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ToServiceGeneratorSolr wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/solr/ToServiceGeneratorSolr.java:67— ClassTooLong — 412 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 12 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: layouts/TableLayout.java jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java— FileTooLong — 1280 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 780 over it, 2.56× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: facade/ToServiceGenerator.java wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java— FileTooLong — 1278 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: ToServiceGenerator (93-2116). The bar is 500 significant lines; this is 778 over it, 2.56× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: rendering/WordRenderer.java jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java— FileTooLong — 1120 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: WordRenderer (115-2026). The bar is 500 significant lines; this is 620 over it, 2.24× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: transfer/TransferToServiceGenerator.java jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java— FileTooLong — 970 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: TransferToServiceGenerator (85-1716). The bar is 500 significant lines; this is 470 over it, 1.94× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: presentation/XMMEditor.java jxfw-eclipse-bundles/bundles/jxfw-metamodel.editor/src/ru/croc/ctp/jxfw/XtendMetaModel/presentation/XMMEditor.java— FileTooLong — 814 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: XMMEditor (168-1818). The bar is 500 significant lines; this is 314 over it, 1.63× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: tree/AreaTreeBuilder.java jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java— FileTooLong — 752 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: AreaTreeBuilder (101-1390). The bar is 500 significant lines; this is 252 over it, 1.50× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: generator/EcoreGenerator.java jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java— FileTooLong — 598 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: EcoreGenerator (74-961). The bar is 500 significant lines; this is 98 over it, 1.20× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: facade/WebClientControllerCreator.java wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java— FileTooLong — 545 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: WebClientControllerCreator (87-682). The bar is 500 significant lines; this is 45 over it, 1.09× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: layoutmanager/GenericLayoutManager.java jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/layout/layoutmanager/GenericLayoutManager.java— FileTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: GenericLayoutManager (34-1095). The bar is 500 significant lines; this is 26 over it, 1.05× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: fowriter/XslFoProfileWriter.java jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/XslFoProfileWriter.java— FileTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: XslFoProfileWriter (36-1271). The bar is 500 significant lines; this is 18 over it, 1.04× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: attribute/AttributeParser.java jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/attribute/AttributeParser.java— FileTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: AttributeParser (89-798). The bar is 500 significant lines; this is 8 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
MethodTooLong: AttributeParser.processProperties jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/attribute/AttributeParser.java:334— MethodTooLong — processProperties runs 241 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 141 over it, 2.41× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebClientControllerCreator.create wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:135— MethodTooLong — create runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BlockProperties.addBlock jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/foproperties/BlockProperties.java:59— MethodTooLong — addBlock runs 177 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AttributeParser.processProperty jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/AttributeParser.java:308— MethodTooLong — processProperty runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: XMMEditor.createPages jxfw-eclipse-bundles/bundles/jxfw-metamodel.editor/src/ru/croc/ctp/jxfw/XtendMetaModel/presentation/XMMEditor.java:1012— MethodTooLong — createPages runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AreaTreeBuilder.parseChildrenElement jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:189— MethodTooLong — parseChildrenElement runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebClientDataSourceCreator.create wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientDataSourceCreator.java:96— MethodTooLong — create runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TransferToServiceGenerator.createToToFieldBlockCode jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:651— MethodTooLong — createToToFieldBlockCode runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ToServiceGenerator.populateNavigables wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1314— MethodTooLong — populateNavigables runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ToServiceGenerator.createToToFieldBlockCode wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:710— MethodTooLong — createToToFieldBlockCode runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WordRenderer.completeListItem jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:859— MethodTooLong — completeListItem runs 105 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 5 over it, 1.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (6 lines × 2) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:413— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:413-418 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/solr/ToServiceGeneratorSolr.java:276-281 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:420` calls `autowireServiceBySetter`, `autowireFieldsBySetters` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/solr/ToServiceGeneratorSolr.java:282` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:630— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:630-635 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:689-694 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1309— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1309-1314 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1596-1601 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/attribute/AttributeParser.java:168— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/attribute/AttributeParser.java:168-173 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/AttributeParser.java:211-216 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/attribute/AttributeParser.java:168` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: `StringUtils` names `org.apache.commons.lang.StringUtils` in one and `org.apache.commons.lang3.StringUtils` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/foproperties/BlockProperties.java:242— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/foproperties/BlockProperties.java:242-247 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/foproperties/BlockProperties.java:252-257 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:748— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:748-753 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:758-763 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/export/impl/BaseExportDataProvider.java:177— jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/export/impl/BaseExportDataProvider.java:177-182 | jxfw-eclipse-bundles/bundles/jxfw-metamodel/src/main/java/ru/croc/ctp/jxfw/metamodel/runtime/impl/XfwModelImpl.java:190-195 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `jxfw-eclipse-bundles/bundles/jxfw-metamodel/src/main/java/ru/croc/ctp/jxfw/metamodel/runtime/impl/XfwModelImpl.java:186` calls `resolveMetadata` and `jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/export/impl/BaseExportDataProvider.java:174` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1573— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1573-1578 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1859-1864 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/store/impl/UnitOfWorkMultiStoreServiceImpl.java:65— jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/store/impl/UnitOfWorkMultiStoreServiceImpl.java:65-70 | jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/store/impl/UnitOfWorkSingleStoreServiceImpl.java:37-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/GenericArea.java:309— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/GenericArea.java:309-315 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/element/root/GenericArea.java:251-256 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java:143— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java:143-148 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/jpa/ToServiceGeneratorJpa.java:154-159 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/jpa/ToServiceGeneratorJpa.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java:143` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:923— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:923-929 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1019-1025 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:923` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1317— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1317-1323 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1604-1610 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/JsModelGenerator.java:469— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/JsModelGenerator.java:469-475 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/JsModelGenerator.java:485-491 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2144— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2144-2150 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2384-2390 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2144` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:951— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:951-957 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:960-966 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:951` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java:155— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java:155-161 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/jpa/ToServiceGeneratorJpa.java:167-173 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/jpa/ToServiceGeneratorJpa.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1350— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1350-1356 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1637-1643 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:241— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:241-247 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:244-250 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:237` calls `builder`, `addMember`, `build` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:241` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportSequenceGroupContextSplitterAndAggregator.java:40— jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportSequenceGroupContextSplitterAndAggregator.java:40-46 | jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/SimpleImportContextSplitterAndAggregator.java:42-48 — before extracting anything, compare `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportSequenceGroupContextSplitterAndAggregator.java` and `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/SimpleImportContextSplitterAndAggregator.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) jxfw-cass-runtime/src/main/java/ru/croc/ctp/jxfw/cass/predicate/CassandraQueryContext.java:43— jxfw-cass-runtime/src/main/java/ru/croc/ctp/jxfw/cass/predicate/CassandraQueryContext.java:43-49 | jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/predicate/SolrQueryContext.java:44-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-cass-runtime/src/main/java/ru/croc/ctp/jxfw/cass/predicate/CassandraQueryContext.java:43` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:348— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:348-363 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:350-365 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:369— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:369-384 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:371-386 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:390— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:390-405 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:392-407 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (16 lines × 2) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java:33— jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java:33-48 | jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImplWithXmlns.java:47-62 — before extracting anything, compare `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java` and `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImplWithXmlns.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java:150— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java:150-165 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/FoFont.java:119-135 — before extracting anything, compare `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java` and `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/FoFont.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java:150` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java:435— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java:435-450 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/FoFont.java:380-395 — before extracting anything, compare `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java` and `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/FoFont.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java:435` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:1208— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:1208-1223 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:1263-1278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:1208` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/exception/dto/ExceptionToSerializer.java:40— jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/exception/dto/ExceptionToSerializer.java:40-55 | jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/exception/dto/XExceptionToSerializer.java:38-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/exception/dto/ExceptionToSerializer.java:40` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `to` to `ExceptionTo` in one and `XExceptionTo` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/exception/dto/ExceptionToSerializer.java:38` calls `writeObjectField`, `getParentClasses` and `jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/exception/dto/XExceptionToSerializer.java:36` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:278— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:278-292 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:281-295 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:278` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:297` calls `addMethod`, `createEqualsObjectMethod`, `build` and `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:294` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:595— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:595-609 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:653-667 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:595` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:592` calls `addStatement` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:652` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:613— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:613-627 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:671-685 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:613` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/formatters/HrefEvaluator.java:73— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/formatters/HrefEvaluator.java:73-87 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/formatters/ImageEvaluator.java:64-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/formatters/HrefEvaluator.java:88` calls `escapeHtml4`, `getCurrentValue`, `toString` and `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/formatters/ImageEvaluator.java:79` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:1050— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:1050-1064 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:1115-1129 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:1050` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1175— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1175-1189 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1203-1217 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: the declarations holding them bind `area` to `PageNumberArea` in one and `PageNumberCitationArea` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (15 lines × 2) jxfw-eclipse-bundles/bundles/jxfw-metamodel.editor/src/ru/croc/ctp/jxfw/XtendMetaModel/presentation/XMMEditor.java:1023— jxfw-eclipse-bundles/bundles/jxfw-metamodel.editor/src/ru/croc/ctp/jxfw/XtendMetaModel/presentation/XMMEditor.java:1023-1037 | jxfw-eclipse-bundles/bundles/jxfw-metamodel.editor/src/ru/croc/ctp/jxfw/XtendMetaModel/presentation/XMMEditor.java:1057-1071 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/list/ListItemBodyArea.java:41— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/list/ListItemBodyArea.java:41-55 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/list/ListItemLabelArea.java:41-55 — before extracting anything, compare `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/list/ListItemBodyArea.java` and `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/list/ListItemLabelArea.java` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:179— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:179-183 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:628-639 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:179` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportSequenceGroupContextSplitterAndAggregator.java:67— jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportSequenceGroupContextSplitterAndAggregator.java:67-71 | jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/SimpleImportContextSplitterAndAggregator.java:98-102 — before extracting anything, compare `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportSequenceGroupContextSplitterAndAggregator.java` and `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/SimpleImportContextSplitterAndAggregator.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportSequenceGroupContextSplitterAndAggregator.java:67` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:908— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:908-912 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:917-921 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:978— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:978-982 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:987-991 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/ExceptionBuilderImpl.java:89— jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/ExceptionBuilderImpl.java:89-94 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/ExceptionBuilderImpl.java:118-122 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/ExceptionBuilderImpl.java:89` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1562— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1562-1566 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1848-1852 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/core/common/AreaType.java:214— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/core/common/AreaType.java:214-218 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/core/common/FoPropertyType.java:569-573 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java:83— jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java:83-87 | jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImplWithXmlns.java:108-112 — before extracting anything, compare `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java` and `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImplWithXmlns.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:490— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:490-500 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:497-507 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:490` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:496` calls `addAnnotation` and `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:489` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:868— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:868-878 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:935-945 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:868` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1597— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1597-1607 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1883-1893 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11 lines × 2) REDACTED:160— REDACTED:160-170 | REDACTED:220-230 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:160` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `request` to `ExecuteImportRequest` in one and `ExecuteExportRequest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/facade/webclient/ReportController.java:60— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/facade/webclient/ReportController.java:60-70 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/facade/webclient/ReportControllerNew.java:61-71 — before extracting anything, compare `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/facade/webclient/ReportController.java` and `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/facade/webclient/ReportControllerNew.java` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/facade/webclient/ReportController.java:60` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/CommonTable.java:118— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/CommonTable.java:118-128 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/TransponedTable.java:129-139 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1398— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1398-1407 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1684-1693 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1398` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientDataSourceCreator.java:175— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientDataSourceCreator.java:175-184 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientDataSourceCreator.java:574-583 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientDataSourceCreator.java:573` calls `equals` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientDataSourceCreator.java:173` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java:54— jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java:54-63 | jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImplWithXmlns.java:79-88 — before extracting anything, compare `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java` and `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImplWithXmlns.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java:54` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/facade/webclient/CriteriaComposer.java:306— jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/facade/webclient/CriteriaComposer.java:306-315 | jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/facade/webclient/CriteriaComposer.java:334-343 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/facade/webclient/CriteriaComposer.java:306` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (10 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/TransponedTable.java:102— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/TransponedTable.java:102-111 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/TransponedTable.java:169-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/TransponedTable.java:102` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/facade/webclient/CriteriaComposer.java:477— jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/facade/webclient/CriteriaComposer.java:477-486 | jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/load/impl/SolrLoadServiceImpl.java:65-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:412— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:412-431 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:420-439 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:410` calls `setFields` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:418` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (20 lines × 2) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:561— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:561-580 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:641-660 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:561` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20 lines × 2) jxfw-eclipse-bundles/bundles/jxfw-metamodel.editor/src/ru/croc/ctp/jxfw/XtendMetaModel/presentation/XMMEditor.java:1104— jxfw-eclipse-bundles/bundles/jxfw-metamodel.editor/src/ru/croc/ctp/jxfw/XtendMetaModel/presentation/XMMEditor.java:1104-1123 | jxfw-eclipse-bundles/bundles/jxfw-metamodel.editor/src/ru/croc/ctp/jxfw/XtendMetaModel/presentation/XMMEditor.java:1174-1193 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-eclipse-bundles/bundles/jxfw-metamodel.editor/src/ru/croc/ctp/jxfw/XtendMetaModel/presentation/XMMEditor.java:1104` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 2) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/impl/sql/H2BitwiseAndSqlFunction.java:21— jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/impl/sql/H2BitwiseAndSqlFunction.java:21-40 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/impl/sql/OracleBitwiseAndSqlFunction.java:21-40 — before extracting anything, compare `jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/impl/sql/H2BitwiseAndSqlFunction.java` and `jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/impl/sql/OracleBitwiseAndSqlFunction.java` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20 lines × 2) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/impl/sql/MySqlBitwiseAndSqlFunction.java:21— jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/impl/sql/MySqlBitwiseAndSqlFunction.java:21-40 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/impl/sql/PostgreSqlBitwiseAndSqlFunction.java:21-40 — before extracting anything, compare `jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/impl/sql/MySqlBitwiseAndSqlFunction.java` and `jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/impl/sql/PostgreSqlBitwiseAndSqlFunction.java` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java:134— jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java:134-147 | jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImplWithXmlns.java:159-172 — before extracting anything, compare `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java` and `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImplWithXmlns.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (14 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:1191— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:1191-1204 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:1246-1259 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:1191` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) jxfw-cass-runtime/src/main/java/ru/croc/ctp/jxfw/cass/load/events/CassBeforeLoadEvent.java:29— jxfw-cass-runtime/src/main/java/ru/croc/ctp/jxfw/cass/load/events/CassBeforeLoadEvent.java:29-42 | jxfw-cass-runtime/src/main/java/ru/croc/ctp/jxfw/cass/load/events/CassPreCheckSecurityEvent.java:29-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/load/events/SolrBeforeLoadEvent.java:29— jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/load/events/SolrBeforeLoadEvent.java:29-42 | jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/load/events/SolrPreCheckSecurityEvent.java:28-41 — before extracting anything, compare `jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/load/events/SolrBeforeLoadEvent.java` and `jxfw-solr-runtime/src/main/java/ru/croc/ctp/jxfw/solr/load/events/SolrPreCheckSecurityEvent.java` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/MasterDetailLayout.java:349— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/MasterDetailLayout.java:349-362 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:929-942 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `layoutProfile` to `MasterDetailLayoutClass` in one and `TableLayoutClass` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (13 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1648— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1648-1660 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1930-1942 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:536— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:536-548 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:638-650 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:536` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:535` calls `addParameter`, `createExpandParameter` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:637` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2333— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2333-2345 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2374-2386 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:577— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:577-589 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1529-1541 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:577` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `area` to `FlowArea` in one and `StaticContentArea` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (13 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1065— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1065-1077 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1141-1153 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1065` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `area` to `ListItemBodyArea` in one and `ListItemLabelArea` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (4 members, 50+ identical tokens) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:364— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:364-385 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:619-638 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1173-1189 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1201-1217 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:139— jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:139-156 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:166-188 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:197-216 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:226-247 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/dialect/XfwH2Dialect.java:58— jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/dialect/XfwH2Dialect.java:58-73 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/dialect/XfwMySqlDialect.java:55-70 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/dialect/XfwOracle10gDialect.java:55-70 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/dialect/XfwPostgreSql9Dialect.java:55-70 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:469— jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:469-485 | jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:487-503 | jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:505-521 | jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:523-539 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (18 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1444— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1444-1461 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1730-1747 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (18 lines × 2) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/jdk7/validator/MaxExclusiveValidator.java:29— jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/jdk7/validator/MaxExclusiveValidator.java:29-46 | jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/validator/MaxExclusiveValidator.java:29-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `LocalDate` names `java.time.LocalDate` in one and `org.threeten.bp.LocalDate` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (18 lines × 2) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/jdk7/validator/MinExclusiveValidator.java:29— jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/jdk7/validator/MinExclusiveValidator.java:29-46 | jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/validator/MinExclusiveValidator.java:29-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `LocalDate` names `java.time.LocalDate` in one and `org.threeten.bp.LocalDate` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (18 lines × 2) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/jdk7/validator/MinInclusiveValidator.java:29— jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/jdk7/validator/MinInclusiveValidator.java:29-46 | jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/validator/MinInclusiveValidator.java:29-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `LocalDate` names `java.time.LocalDate` in one and `org.threeten.bp.LocalDate` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17 lines × 2) REDACTED:184— REDACTED:184-200 | REDACTED:233-249 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:184` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (17 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1037— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1037-1053 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1119-1135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1037` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `area` to `ListItemBodyArea` in one and `ListItemLabelArea` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (17 lines × 2) jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:138— jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:138-154 | jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:199-215 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:138` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/jdk7/validator/MaxInclusiveValidator.java:29— jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/jdk7/validator/MaxInclusiveValidator.java:29-45 | jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/validator/MaxInclusiveValidator.java:29-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit. Note first that the copies are not typed on the same thing: `LocalDate` names `java.time.LocalDate` in one and `org.threeten.bp.LocalDate` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1581— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1581-1589 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1867-1875 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:825— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:825-833 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1681-1689 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:825` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `tableNode` to `Table` in one and `XslfoTable` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9 lines × 2) jxfw-eclipse-bundles/bundles/jxfw-metamodel/src/main/java/ru/croc/ctp/jxfw/metamodel/runtime/impl/XfwEnumerationImpl.java:129— jxfw-eclipse-bundles/bundles/jxfw-metamodel/src/main/java/ru/croc/ctp/jxfw/metamodel/runtime/impl/XfwEnumerationImpl.java:129-137 | jxfw-eclipse-bundles/bundles/jxfw-metamodel/src/main/java/ru/croc/ctp/jxfw/metamodel/runtime/impl/XfwEnumerationImpl.java:195-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-eclipse-bundles/bundles/jxfw-metamodel/src/main/java/ru/croc/ctp/jxfw/metamodel/runtime/impl/XfwEnumerationImpl.java:129` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/exception/dto/ExceptionToSerializer.java:57— jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/exception/dto/ExceptionToSerializer.java:57-65 | jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/exception/dto/XExceptionToSerializer.java:55-63 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (30 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:746— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:746-775 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:799-828 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:746` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1253— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1253-1282 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1539-1568 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1253` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (30 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2456— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2456-2485 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2538-2567 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2456` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:847— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:847-858 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:916-927 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:938— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:938-949 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1034-1045 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:938` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/load/events/JpaBeforeLoadEvent.java:29— jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/load/events/JpaBeforeLoadEvent.java:29-40 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/load/events/JpaPreCheckSecurityEvent.java:29-41 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/facade/webclient/impl/DomainFacadeIgnoreServiceImpl.java:128— jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/facade/webclient/impl/DomainFacadeIgnoreServiceImpl.java:128-134 | jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1063-1069 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1151-1157 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `facadeIgnoreAnnotation` to `XfwAnnotation` in one and `EAnnotation` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 3) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1078— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1078-1084 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1154-1160 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1435-1441 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1078` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `area` to `ListItemBodyArea` in one and `ListItemLabelArea` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 3) jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/impl/DataSourceClassEcoreGenerator.java:54— jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/impl/DataSourceClassEcoreGenerator.java:54-60 | jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/impl/DataSourceEcoreGenerator.java:64-70 | jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/impl/EnumEcoreGenerator.java:38-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/impl/DataSourceClassEcoreGenerator.java:54` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/table/XslfoTable.java:366— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/table/XslfoTable.java:366-371 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/table/XslfoTable.java:380-385 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/table/XslfoTable.java:636-641 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/table/XslfoTable.java:652-657 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/table/XslfoTable.java:366` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/table/XslfoTable.java:643` calls `getRowFormat`, `getBorders`, `setLineStyle` and `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/table/XslfoTable.java:373` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 4) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:141— jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:141-146 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:168-174 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:199-204 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:228-234 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:175` calls `group` and `jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:148` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 4) jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:474— jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:474-479 | jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:492-497 | jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:510-515 | jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:528-533 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:474` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
AttributeParser.processBorderAttribute (cognitive 27) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/attribute/AttributeParser.java:166— AttributeParser.processBorderAttribute has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 4 (5 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AttributeParser.processBorderAttribute (cognitive 27) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/AttributeParser.java:210— AttributeParser.processBorderAttribute has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 4 (5 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (27 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:209— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:209-235 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:215-241 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:237` calls `builder`, `addMember`, `build` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:242` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (27 lines × 2) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportSequenceGroupContextSplitterAndAggregator.java:74— jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportSequenceGroupContextSplitterAndAggregator.java:74-100 | jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/SimpleImportContextSplitterAndAggregator.java:105-131 — before extracting anything, compare `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportSequenceGroupContextSplitterAndAggregator.java` and `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/SimpleImportContextSplitterAndAggregator.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportSequenceGroupContextSplitterAndAggregator.java:74` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:552— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:552-570 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:561-579 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:552` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (19 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:918— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:918-936 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:988-1006 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:918` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–16 lines × 2) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:666— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:666-676 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1024-1039 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:666` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–16 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:608— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:608-618 | jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:928-943 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:608` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–10 lines × 2) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/solr/ToServiceGeneratorSolr.java:530— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/solr/ToServiceGeneratorSolr.java:530-539 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/solr/ToServiceGeneratorSolr.java:552-560 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/solr/ToServiceGeneratorSolr.java:530` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9–10 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/TransponedTable.java:91— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/TransponedTable.java:91-99 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/TransponedTable.java:157-166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/TransponedTable.java:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:140— jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:140-147 | jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:201-208 | jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:261-268 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:140` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:145— jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:145-152 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:174-181 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:233-240 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
AttributeParser.processProperties (cyclomatic 109) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/attribute/AttributeParser.java:334— AttributeParser.processProperties has cyclomatic complexity 109 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
TableLayout.writeTotalRow (cyclomatic 77) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2225— TableLayout.writeTotalRow has cyclomatic complexity 77 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AttributeParser.processProperty (cyclomatic 77) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/AttributeParser.java:308— AttributeParser.processProperty has cyclomatic complexity 77 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
XslFoTreeBuilder.parseChildrenElement (cyclomatic 67) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/XslFoTreeBuilder.java:116— XslFoTreeBuilder.parseChildrenElement has cyclomatic complexity 67 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
XslfoTable.setHeaderBodyFooterBordersProperties (cyclomatic 65) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/table/XslfoTable.java:460— XslfoTable.setHeaderBodyFooterBordersProperties has cyclomatic complexity 65 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
TableLayout.writeGroupBound (cyclomatic 57) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:1713— TableLayout.writeGroupBound has cyclomatic complexity 57 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BlockProperties.addBlock (cyclomatic 54) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/foproperties/BlockProperties.java:59— BlockProperties.addBlock has cyclomatic complexity 54 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
JsModelGenerator.getTypeName (cyclomatic 38) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/JsModelGenerator.java:238— JsModelGenerator.getTypeName has cyclomatic complexity 38 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
AbstractEcoreGenerator.getEType (cyclomatic 37) jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/AbstractEcoreGenerator.java:143— AbstractEcoreGenerator.getEType has cyclomatic complexity 37 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
GenericArea.preProcessProperties (cyclomatic 33) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/GenericArea.java:441— GenericArea.preProcessProperties has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ReportParameterConverter.parse (cyclomatic 33) jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/ReportParameterConverter.java:177— ReportParameterConverter.parse has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AreaTreeBuilder.parseChildrenElement (cyclomatic 32) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:189— AreaTreeBuilder.parseChildrenElement has cyclomatic complexity 32 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
WordRenderer.completeListItem (cyclomatic 32) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:859— WordRenderer.completeListItem has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WordRenderer.treeRenderer (cyclomatic 30) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:183— WordRenderer.treeRenderer has cyclomatic complexity 30 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
GenericLayoutManager.calculateAreaSize (cyclomatic 29) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/layout/layoutmanager/GenericLayoutManager.java:123— GenericLayoutManager.calculateAreaSize has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToServiceGenerator.createPropertyValueByType (cyclomatic 27) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1473— ToServiceGenerator.createPropertyValueByType has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TransferToServiceGenerator.createPropertyValueByType (cyclomatic 27) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1187— TransferToServiceGenerator.createPropertyValueByType has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ListItemArea.postProcessProperties (cyclomatic 27) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/list/ListItemArea.java:43— ListItemArea.postProcessProperties has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PredicateComposer.getOperator (cyclomatic 26) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposer.java:307— PredicateComposer.getOperator has cyclomatic complexity 26 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ExcelRenderer.renderAreaToCells (cyclomatic 25) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/rendering/excel/ExcelRenderer.java:233— ExcelRenderer.renderAreaToCells has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PredicateComposer.createPredicate (cyclomatic 24) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposer.java:103— PredicateComposer.createPredicate has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EcoreGenerator.addRelationAnnotation (cyclomatic 24) jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:822— EcoreGenerator.addRelationAnnotation has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TableLayout.writeSubTitleRow (cyclomatic 23) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2076— TableLayout.writeSubTitleRow has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WordRenderer.addTableCell (cyclomatic 23) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1776— WordRenderer.addTableCell has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
XfwMetadataHolder.init (cyclomatic 22) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/metadata/XfwMetadataHolder.java:89— XfwMetadataHolder.init has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FoFont.setFontSize (cyclomatic 21) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java:184— FoFont.setFontSize has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
AreaTreeBuilder.processStaticContentArea (cyclomatic 21) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:518— AreaTreeBuilder.processStaticContentArea has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BlockProperties.completeBlock (cyclomatic 21) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/foproperties/BlockProperties.java:323— BlockProperties.completeBlock has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LayoutTable.getAggregatedValue (cyclomatic 20) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/LayoutTable.java:119— LayoutTable.getAggregatedValue has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TableLayout.writeRows (cyclomatic 20) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:1302— TableLayout.writeRows has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ListItemArea.calculateMargins (cyclomatic 20) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/element/pagesequence/listblock/ListItemArea.java:110— ListItemArea.calculateMargins has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TableProperties.setSpannedForCell (cyclomatic 20) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/foproperties/TableProperties.java:144— TableProperties.setSpannedForCell has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WordRenderer.addCatchWord (cyclomatic 20) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1323— WordRenderer.addCatchWord has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AttributeParser.processShorthandProperties (cyclomatic 19) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/attribute/AttributeParser.java:272— AttributeParser.processShorthandProperties has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
TransferPropertyResolverImpl.addTypedValue (cyclomatic 18) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferPropertyResolverImpl.java:24— TransferPropertyResolverImpl.addTypedValue has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
XslFoProfileWriter.writeLayoutMaster (cyclomatic 18) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/XslFoProfileWriter.java:380— XslFoProfileWriter.writeLayoutMaster has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GenericArea.moveChildMarginsToParentPaddings (cyclomatic 18) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/GenericArea.java:752— GenericArea.moveChildMarginsToParentPaddings has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: GenericArea.getDefaultPropertyValue (cyclomatic 27) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
DataSourceEcoreGenerator.setupParametersOfDataSource (cyclomatic 18) jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/impl/DataSourceEcoreGenerator.java:124— DataSourceEcoreGenerator.setupParametersOfDataSource has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
XslFoProfileWriter.setRegionAttributes (cyclomatic 17) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/XslFoProfileWriter.java:1168— XslFoProfileWriter.setRegionAttributes has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ReportParam.setValue (cyclomatic 17) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/impl/ReportParams.java:150— ReportParam.setValue has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GenericLayoutManager.calculateTableWidthFromCells (cyclomatic 17) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/layout/layoutmanager/GenericLayoutManager.java:700— GenericLayoutManager.calculateTableWidthFromCells has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WebClientDataSourceCreator.generateControllerMethod (cyclomatic 16) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientDataSourceCreator.java:259— WebClientDataSourceCreator.generateControllerMethod has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
JsModelGenerator.getTypeParams (cyclomatic 16) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/JsModelGenerator.java:144— JsModelGenerator.getTypeParams has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PageBootloader.parseLoaderConfig (cyclomatic 16) jxfw-wc-loader/src/main/java/ru/croc/ctp/jxfw/wc/web/bootloader/PageBootloader.java:46— PageBootloader.parseLoaderConfig has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TableLayout.insertColumn (cyclomatic 16) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:1182— TableLayout.insertColumn has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
InlineAreasExcelRenderer.handleValueTypeAndSetText (cyclomatic 16) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/rendering/excel/InlineAreasExcelRenderer.java:210— InlineAreasExcelRenderer.handleValueTypeAndSetText has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BaseExportDataProvider.formatPrimitive (cyclomatic 16) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/export/impl/BaseExportDataProvider.java:113— BaseExportDataProvider.formatPrimitive has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TableLayout.writeTotalRow (cognitive 366) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2225— TableLayout.writeTotalRow has cognitive complexity 366 (threshold 15). Drivers by points: if/else 68 (310 pts), loops 9 (44 pts), ternaries 2 (5 pts), boolean chains 4, error handling 1 (3 pts) (nesting depth added 282). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java holds 10 of the 121 methods over the threshold — including the worst — and 711 of the 2284 points over it (31%), 4.8× the next-largest file (jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java at 147). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
TableLayout.writeGroupBound (cognitive 200) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:1713— TableLayout.writeGroupBound has cognitive complexity 200 (threshold 15). Drivers by points: if/else 39 (160 pts), loops 11 (29 pts), match/switch 2 (6 pts), boolean chains 5 (nesting depth added 143). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java holds 10 of the 121 methods over the threshold — including the worst — and 711 of the 2284 points over it (31%), 4.8× the next-largest file (jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java at 147). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
XslfoTable.setHeaderBodyFooterBordersProperties (cognitive 125) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/table/XslfoTable.java:460— XslfoTable.setHeaderBodyFooterBordersProperties has cognitive complexity 125 (threshold 15). Drivers by points: if/else 25 (53 pts), loops 15 (48 pts), boolean chains 24 (nesting depth added 61). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlockProperties.addBlock (cognitive 91) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/foproperties/BlockProperties.java:59— BlockProperties.addBlock has cognitive complexity 91 (threshold 15). Drivers by points: if/else 30 (70 pts), loops 3 (8 pts), boolean chains 6, ternaries 3 (4 pts), match/switch 1 (3 pts) (nesting depth added 48). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PredicateComposer.createPredicate (cognitive 85) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposer.java:103— PredicateComposer.createPredicate has cognitive complexity 85 (threshold 15). Drivers by points: if/else 18 (53 pts), ternaries 4 (24 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 57). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TableLayout.writeRows (cognitive 81) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:1302— TableLayout.writeRows has cognitive complexity 81 (threshold 15). Drivers by points: if/else 14 (50 pts), ternaries 4 (16 pts), loops 4 (14 pts), boolean chains 1 (nesting depth added 58). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java holds 10 of the 121 methods over the threshold — including the worst — and 711 of the 2284 points over it (31%), 4.8× the next-largest file (jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java at 147). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
XslFoTreeBuilder.parseChildrenElement (cognitive 80) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/XslFoTreeBuilder.java:116— XslFoTreeBuilder.parseChildrenElement has cognitive complexity 80 (threshold 15). Drivers by points: if/else 24 (65 pts), boolean chains 12, match/switch 1 (2 pts), loops 1 (nesting depth added 42). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReportParameterConverter.parse (cognitive 80) jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/ReportParameterConverter.java:177— ReportParameterConverter.parse has cognitive complexity 80 (threshold 15). Drivers by points: if/else 13 (42 pts), error handling 10 (35 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 55). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XslFoProfileWriter.writeLayoutMaster (cognitive 62) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/XslFoProfileWriter.java:380— XslFoProfileWriter.writeLayoutMaster has cognitive complexity 62 (threshold 15). Drivers by points: if/else 12 (38 pts), ternaries 4 (20 pts), error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 44). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
WordRenderer.completeListItem (cognitive 62) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:859— WordRenderer.completeListItem has cognitive complexity 62 (threshold 15). Drivers by points: if/else 17 (41 pts), loops 5 (14 pts), boolean chains 4, match/switch 1 (3 pts) (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TableLayout.writeSubTitleRow (cognitive 59) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2076— TableLayout.writeSubTitleRow has cognitive complexity 59 (threshold 15). Drivers by points: if/else 16 (44 pts), loops 3 (8 pts), error handling 1 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 36). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This file is where this pass's cognitive complexity CONCENTRATES: jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java holds 10 of the 121 methods over the threshold — including the worst — and 711 of the 2284 points over it (31%), 4.8× the next-largest file (jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java at 147). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ToServiceGenerator.createPropertyValueByType (cognitive 52) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1473— ToServiceGenerator.createPropertyValueByType has cognitive complexity 52 (threshold 15). Drivers by points: if/else 21 (28 pts), ternaries 1 (17 pts), boolean chains 7 (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TransferToServiceGenerator.createPropertyValueByType (cognitive 52) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1187— TransferToServiceGenerator.createPropertyValueByType has cognitive complexity 52 (threshold 15). Drivers by points: if/else 21 (28 pts), ternaries 1 (17 pts), boolean chains 7 (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TableProperties.setSpannedForCell (cognitive 52) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/foproperties/TableProperties.java:144— TableProperties.setSpannedForCell has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (42 pts), loops 3 (7 pts), boolean chains 3 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GenericLayoutManager.calculateAreaSize (cognitive 49) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/layout/layoutmanager/GenericLayoutManager.java:123— GenericLayoutManager.calculateAreaSize has cognitive complexity 49 (threshold 15). Drivers by points: if/else 20 (37 pts), ternaries 3 (5 pts), boolean chains 3, match/switch 1 (3 pts), loops 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataSourceEcoreGenerator.setupParametersOfDataSource (cognitive 47) jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/impl/DataSourceEcoreGenerator.java:124— DataSourceEcoreGenerator.setupParametersOfDataSource has cognitive complexity 47 (threshold 15). Drivers by points: if/else 18 (38 pts), loops 3 (7 pts), boolean chains 1, ternaries 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TableLayout.hideColumns (cognitive 46) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:1034— TableLayout.hideColumns has cognitive complexity 46 (threshold 15). Drivers by points: if/else 10 (40 pts), loops 3 (6 pts) (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java holds 10 of the 121 methods over the threshold — including the worst — and 711 of the 2284 points over it (31%), 4.8× the next-largest file (jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java at 147). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
EcoreGenerator.addRelationAnnotation (cognitive 45) jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:822— EcoreGenerator.addRelationAnnotation has cognitive complexity 45 (threshold 15). Drivers by points: if/else 18 (35 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DomainToXmlParser.parseDomainTo (cognitive 42) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/xml/DomainToXmlParser.java:27— DomainToXmlParser.parseDomainTo has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (34 pts), loops 2 (7 pts), boolean chains 1 (nesting depth added 28). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AreaTreeBuilder.processStaticContentArea (cognitive 42) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:518— AreaTreeBuilder.processStaticContentArea has cognitive complexity 42 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 4 (10 pts), ternaries 2 (5 pts), match/switch 2 (4 pts), boolean chains 3 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReportParameterConverter.format (cognitive 41) jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/ReportParameterConverter.java:72— ReportParameterConverter.format has cognitive complexity 41 (threshold 15). Drivers by points: if/else 18 (40 pts), boolean chains 1 (nesting depth added 22). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GenericArea.preProcessProperties (cognitive 40) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/GenericArea.java:441— GenericArea.preProcessProperties has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 8 (24 pts), if/else 5 (10 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ListItemArea.postProcessProperties (cognitive 39) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/list/ListItemArea.java:43— ListItemArea.postProcessProperties has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (25 pts), ternaries 5 (10 pts), boolean chains 4 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ImportSequenceGroupContextSplitterAndAggregator.topologicalSort (cognitive 38) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/imp/context/ImportSequenceGroupContextSplitterAndAggregator.java:109— ImportSequenceGroupContextSplitterAndAggregator.topologicalSort has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (25 pts), loops 4 (10 pts), ternaries 1 (3 pts) (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GenericArea.moveChildMarginsToParentPaddings (cognitive 38) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/GenericArea.java:752— GenericArea.moveChildMarginsToParentPaddings has cognitive complexity 38 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 4 (14 pts), boolean chains 4, match/switch 1 (nesting depth added 23). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ExcelRenderer.renderAreaToCells (cognitive 38) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/rendering/excel/ExcelRenderer.java:233— ExcelRenderer.renderAreaToCells has cognitive complexity 38 (threshold 15). Drivers by points: if/else 18 (25 pts), loops 2 (6 pts), boolean chains 5, ternaries 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WordRenderer.addCatchWord (cognitive 37) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1323— WordRenderer.addCatchWord has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (26 pts), ternaries 2 (6 pts), match/switch 1 (3 pts), loops 1 (2 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XfwXslfoReport.writeReport (cognitive 36) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/impl/XfwXslfoReport.java:570— XfwXslfoReport.writeReport has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (34 pts), loops 1 (2 pts) (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MasterDetailLayout.writeLayout (cognitive 36) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/MasterDetailLayout.java:82— MasterDetailLayout.writeLayout has cognitive complexity 36 (threshold 15). Drivers by points: if/else 5 (21 pts), loops 4 (15 pts) (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LayoutTable.getAggregatedValue (cognitive 35) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/LayoutTable.java:119— LayoutTable.getAggregatedValue has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (26 pts), boolean chains 3, match/switch 1 (3 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TableLayout.writeGroupBoundSeparatorEx (cognitive 35) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2741— TableLayout.writeGroupBoundSeparatorEx has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 5 (11 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java holds 10 of the 121 methods over the threshold — including the worst — and 711 of the 2284 points over it (31%), 4.8× the next-largest file (jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java at 147). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
AttributeParser.processProperties (cognitive 35) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/attribute/AttributeParser.java:334— AttributeParser.processProperties has cognitive complexity 35 (threshold 15). Drivers by points: if/else 16 (34 pts), match/switch 1 (nesting depth added 18). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WordRenderer.addPage (cognitive 35) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1227— WordRenderer.addPage has cognitive complexity 35 (threshold 15). Drivers by points: if/else 9 (24 pts), ternaries 2 (8 pts), error handling 1 (3 pts) (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
JsModelGenerator.getTypeParams (cognitive 34) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/JsModelGenerator.java:144— JsModelGenerator.getTypeParams has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (32 pts), boolean chains 2 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PageBootloader.parseLoaderConfig (cognitive 33) jxfw-wc-loader/src/main/java/ru/croc/ctp/jxfw/wc/web/bootloader/PageBootloader.java:46— PageBootloader.parseLoaderConfig has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (28 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
XfwMetadataHolder.init (cognitive 33) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/metadata/XfwMetadataHolder.java:89— XfwMetadataHolder.init has cognitive complexity 33 (threshold 15). Drivers by points: if/else 14 (23 pts), loops 3 (4 pts), boolean chains 3, error handling 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GenericLayoutManager.calculateTableWidthFromCells (cognitive 31) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/layout/layoutmanager/GenericLayoutManager.java:700— GenericLayoutManager.calculateTableWidthFromCells has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 6 (11 pts), boolean chains 3 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BlockProperties.completeBlock (cognitive 31) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/foproperties/BlockProperties.java:323— BlockProperties.completeBlock has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 4, match/switch 1 (3 pts), loops 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XslFoProfileWriter.setRegionAttributes (cognitive 30) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/XslFoProfileWriter.java:1168— XslFoProfileWriter.setRegionAttributes has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (30 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WordRenderer.addListBlock (cognitive 30) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:679— WordRenderer.addListBlock has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 3 (8 pts), match/switch 1 (3 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EcoreGenerator.generate (cognitive 30) jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:140— EcoreGenerator.generate has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (17 pts), ternaries 4 (11 pts), boolean chains 1, loops 1 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GenericLayoutManager.calculateTableHeightFromCells (cognitive 29) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/layout/layoutmanager/GenericLayoutManager.java:786— GenericLayoutManager.calculateTableHeightFromCells has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 4 (10 pts), boolean chains 3 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ListItemArea.calculateMargins (cognitive 29) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/element/pagesequence/listblock/ListItemArea.java:110— ListItemArea.calculateMargins has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (19 pts), ternaries 2 (6 pts), boolean chains 4 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WordRenderer.calcShapeSize (cognitive 29) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:431— WordRenderer.calcShapeSize has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 4 (18 pts), if/else 5, loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WordRenderer.addTableCell (cognitive 28) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1776— WordRenderer.addTableCell has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (18 pts), match/switch 3 (8 pts), loops 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RuntimeComparator.compare (cognitive 28) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/store/impl/comparator/RuntimeComparator.java:20— RuntimeComparator.compare has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (20 pts), error handling 1 (5 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ExcelView.setupStyles (cognitive 28) jxfw-export-poi/src/main/java/ru/croc/ctp/jxfw/export/poi/impl/views/ExcelView.java:147— ExcelView.setupStyles has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 4 (8 pts), boolean chains 2, error handling 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PageBootloader.parseRuntimeMatchSpec (cognitive 27) jxfw-wc-loader/src/main/java/ru/croc/ctp/jxfw/wc/web/bootloader/PageBootloader.java:277— PageBootloader.parseRuntimeMatchSpec has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (19 pts), error handling 1 (6 pts), loops 1 (2 pts) (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
AreaTreeBuilder.processInstreamForeignObject (cognitive 26) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:890— AreaTreeBuilder.processInstreamForeignObject has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 8 (20 pts), if/else 3, boolean chains 2, error handling 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ExcelRenderer.renderImage (cognitive 26) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/rendering/excel/ExcelRenderer.java:411— ExcelRenderer.renderImage has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 5 (nesting depth added 11). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
InlineAreasExcelRenderer.handleValueTypeAndSetText (cognitive 26) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/rendering/excel/InlineAreasExcelRenderer.java:210— InlineAreasExcelRenderer.handleValueTypeAndSetText has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (16 pts), error handling 2 (7 pts), boolean chains 2, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XMMEditor.updateProblemIndication (cognitive 26) jxfw-eclipse-bundles/bundles/jxfw-metamodel.editor/src/ru/croc/ctp/jxfw/XtendMetaModel/presentation/XMMEditor.java:616— XMMEditor.updateProblemIndication has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 2 (8 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransferPropertyResolverImpl.addTypedValue (cognitive 25) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferPropertyResolverImpl.java:24— TransferPropertyResolverImpl.addTypedValue has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (22 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DebugComparators.verifyTransitivity (cognitive 25) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/store/impl/comparator/DebugComparators.java:31— DebugComparators.verifyTransitivity has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 5 (9 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToServiceGenerator.populateNavigables (cognitive 24) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1314— ToServiceGenerator.populateNavigables has cognitive complexity 24 (threshold 15). Drivers by points: if/else 16 (23 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FoColor.getColorFromString (cognitive 24) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/core/common/FoColor.java:99— FoColor.getColorFromString has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 3 (9 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AreaTreeBuilder.processFlowWithStaticContentAreas (cognitive 24) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:424— AreaTreeBuilder.processFlowWithStaticContentAreas has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 3 (5 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XslfoTable.setTableBordersProperties (cognitive 24) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/table/XslfoTable.java:415— XslfoTable.setTableBordersProperties has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 5 (11 pts), boolean chains 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XfwMetadataHolder.buildColumnsToFieldsMap (cognitive 24) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/metadata/XfwMetadataHolder.java:244— XfwMetadataHolder.buildColumnsToFieldsMap has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), error handling 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToServiceGenerator.createToToFieldBlockCode (cognitive 23) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:710— ToServiceGenerator.createToToFieldBlockCode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
WebClientDataSourceCreator.generateControllerMethod (cognitive 23) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientDataSourceCreator.java:259— WebClientDataSourceCreator.generateControllerMethod has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (10 pts), loops 4 (8 pts), boolean chains 2, match/switch 2, ternaries 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
WebClientCookieLocaleResolver.parseLocaleCookieIfNecessary (cognitive 23) jxfw-wc-loader/src/main/java/ru/croc/ctp/jxfw/wc/config/locale/WebClientCookieLocaleResolver.java:59— WebClientCookieLocaleResolver.parseLocaleCookieIfNecessary has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 4 (11 pts) (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PageBootloader.parseFilesMatchConfig (cognitive 23) jxfw-wc-loader/src/main/java/ru/croc/ctp/jxfw/wc/web/bootloader/PageBootloader.java:133— PageBootloader.parseFilesMatchConfig has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (22 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransferToServiceGenerator.createToToFieldBlockCode (cognitive 23) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:651— TransferToServiceGenerator.createToToFieldBlockCode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
FoBorder.changeStyle (cognitive 23) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/border/FoBorder.java:203— FoBorder.changeStyle has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 3 (11 pts), if/else 5 (7 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
CommonTable.pasteColumnsGroup (cognitive 22) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/CommonTable.java:235— CommonTable.pasteColumnsGroup has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 2, boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XfwHelp.documentSynopsys (cognitive 22) jxfw-cli/src/main/java/ru/croc/ctp/jxfw/cli/command/XfwHelp.java:138— XfwHelp.documentSynopsys has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TableLayout.calculateTotalCell (cognitive 21) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:1596— TableLayout.calculateTotalCell has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, ternaries 1 (2 pts), error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java holds 10 of the 121 methods over the threshold — including the worst — and 711 of the 2284 points over it (31%), 4.8× the next-largest file (jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java at 147). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
GenericLayoutManager.doCalculateAreaCoordinates (cognitive 21) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/layout/layoutmanager/GenericLayoutManager.java:868— GenericLayoutManager.doCalculateAreaCoordinates has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (5 pts), match/switch 1 (2 pts), boolean chains 1, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WordRenderer.addTableRow (cognitive 21) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1958— WordRenderer.addTableRow has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XMMEditor.handleChangedResources (cognitive 21) jxfw-eclipse-bundles/bundles/jxfw-metamodel.editor/src/ru/croc/ctp/jxfw/XtendMetaModel/presentation/XMMEditor.java:579— XMMEditor.handleChangedResources has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (13 pts), error handling 1 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbstractEcoreGenerator.getEType (cognitive 21) jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/AbstractEcoreGenerator.java:143— AbstractEcoreGenerator.getEType has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 1 (2 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ToServiceGenerator.populateOpposite (cognitive 20) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1203— ToServiceGenerator.populateOpposite has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LayoutFinder.findLayout (cognitive 20) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/LayoutFinder.java:43— LayoutFinder.findLayout has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (17 pts), boolean chains 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MasterDetailLayout.writeMasterData (cognitive 20) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/MasterDetailLayout.java:143— MasterDetailLayout.writeMasterData has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (7 pts), boolean chains 1, ternaries 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TableLayout.setVarValues (cognitive 20) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2884— TableLayout.setVarValues has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (6 pts), match/switch 1 (3 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java holds 10 of the 121 methods over the threshold — including the worst — and 711 of the 2284 points over it (31%), 4.8× the next-largest file (jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java at 147). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ReportParamDefintionProcessor.processAnd (cognitive 20) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/paramprocessors/ReportParamDefintionProcessor.java:50— ReportParamDefintionProcessor.processAnd has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (6 pts), ternaries 1 (5 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ReportParamDefintionProcessor.processAndNot) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ReportParamDefintionProcessor.processAndNot (cognitive 20) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/paramprocessors/ReportParamDefintionProcessor.java:68— ReportParamDefintionProcessor.processAndNot has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 2 (6 pts), ternaries 1 (5 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ReportParamDefintionProcessor.processAnd) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ExcelView.fillHeaderAndRows (cognitive 20) jxfw-export-poi/src/main/java/ru/croc/ctp/jxfw/export/poi/impl/views/ExcelView.java:240— ExcelView.fillHeaderAndRows has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (7 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BootloaderController.index (cognitive 19) jxfw-wc-loader/src/main/java/ru/croc/ctp/jxfw/wc/web/mvc/controllers/BootloaderController.java:65— BootloaderController.index has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Catchword.doExecute (cognitive 19) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/common/catchword/Catchword.java:54— Catchword.doExecute has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2, loops 1 (2 pts), ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GenericLayoutManager.processTableColumnsProperties (cognitive 19) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/layout/layoutmanager/GenericLayoutManager.java:494— GenericLayoutManager.processTableColumnsProperties has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (15 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
AttributeParser.processProperty (cognitive 19) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/AttributeParser.java:308— AttributeParser.processProperty has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), error handling 1 (2 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
WordRenderer.addFlow (cognitive 19) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:559— WordRenderer.addFlow has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EcoreModelEmitterSolr.addKeyFieldDetails (cognitive 19) jxfw-fulltext-service/src/main/java/ru/croc/ctp/jxfw/fulltext/generator/solr/EcoreModelEmitterSolr.java:67— EcoreModelEmitterSolr.addKeyFieldDetails has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JsModelGenerator.appendDefaultValue (cognitive 18) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/generator/JsModelGenerator.java:202— JsModelGenerator.appendDefaultValue has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 1 (4 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EnumGenerator.generate (cognitive 18) modelgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/mojo/modelgen/EnumGenerator.java:71— EnumGenerator.generate has cognitive complexity 18 (threshold 15). Drivers by points: loops 4 (12 pts), if/else 1 (3 pts), ternaries 1 (3 pts) (nesting depth added 12). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
TaskExecutorWithInterrupt.<init> (cognitive 18) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/impl/TaskExecutorWithInterrupt.java:59— TaskExecutorWithInterrupt.<init> has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (6 pts), error handling 2 (5 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransferToTransformerImplWithXmlns.toXml (cognitive 18) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImplWithXmlns.java:42— TransferToTransformerImplWithXmlns.toXml has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 1 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransponedTable.addCell (cognitive 18) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/TransponedTable.java:123— TransponedTable.addCell has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XmlTextReader.skip (cognitive 18) REDACTED:224— XmlTextReader.skip has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GenericLayoutManager.makeEqualChildrenSizes (cognitive 18) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/layout/layoutmanager/GenericLayoutManager.java:255— GenericLayoutManager.makeEqualChildrenSizes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), match/switch 2 (5 pts), loops 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AreaTreeBuilder.parseChildrenElement (cognitive 18) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:189— AreaTreeBuilder.parseChildrenElement has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), match/switch 1 (2 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExcelRenderer.setPageBreak (cognitive 18) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/rendering/excel/ExcelRenderer.java:512— ExcelRenderer.setPageBreak has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ListItemArea.adjustPaddings (cognitive 18) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/element/pagesequence/listblock/ListItemArea.java:44— ListItemArea.adjustPaddings has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WordRenderer.addRegionBody (cognitive 18) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1467— WordRenderer.addRegionBody has cognitive complexity 18 (threshold 15). Drivers by points: error handling 1 (5 pts), loops 2 (5 pts), if/else 3 (4 pts), match/switch 1 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExceptionDescriptorImpl.updateTableMetadataFromStoreContext (cognitive 18) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/ExceptionDescriptorImpl.java:122— ExceptionDescriptorImpl.updateTableMetadataFromStoreContext has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (18 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PackageModel.getImports (cognitive 17) modelgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/mojo/modelgen/ModelGenerator.java:214— PackageModel.getImports has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (5 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransponedTable.pasteColumnsGroup (cognitive 17) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/fowriter/TransponedTable.java:255— TransponedTable.pasteColumnsGroup has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TableLayout.insertColumn (cognitive 17) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:1182— TableLayout.insertColumn has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (8 pts), boolean chains 5, if/else 2, loops 1 (2 pts) (nesting depth added 2). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cognitive complexity CONCENTRATES: jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java holds 10 of the 121 methods over the threshold — including the worst — and 711 of the 2284 points over it (31%), 4.8× the next-largest file (jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java at 147). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
InstreamForeignObjectArea.createSvg2Image (cognitive 17) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/element/pagesequence/block/InstreamForeignObjectArea.java:66— InstreamForeignObjectArea.createSvg2Image has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WordRenderer.addTable (cognitive 17) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1561— WordRenderer.addTable has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 1 (3 pts), loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BaseExportDataProvider.formatPrimitive (cognitive 17) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/export/impl/BaseExportDataProvider.java:113— BaseExportDataProvider.formatPrimitive has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 4, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AbstractDomainObjectFactory.create (cognitive 17) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/facade/webclient/AbstractDomainObjectFactory.java:52— AbstractDomainObjectFactory.create has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MaxValidatorForNumber.isValid (cognitive 17) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/validator/MaxValidatorForNumber.java:25— MaxValidatorForNumber.isValid has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MinValidatorForNumber.isValid (cognitive 17) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/validation/validator/MinValidatorForNumber.java:26— MinValidatorForNumber.isValid has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EcoreGenerator.setupFieldsOfClass (cognitive 17) jxfw-core-compile/src/main/java/ru/croc/ctp/jxfw/core/generator/EcoreGenerator.java:227— EcoreGenerator.setupFieldsOfClass has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 1 (5 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XfwHelp.documentOptions (cognitive 17) jxfw-cli/src/main/java/ru/croc/ctp/jxfw/cli/command/XfwHelp.java:177— XfwHelp.documentOptions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PageBootloader.parseConfigMatchSpec (cognitive 16) jxfw-wc-loader/src/main/java/ru/croc/ctp/jxfw/wc/web/bootloader/PageBootloader.java:174— PageBootloader.parseConfigMatchSpec has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), boolean chains 4, error handling 1 (3 pts), match/switch 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScriptMatcher.isMatch (cognitive 16) jxfw-wc-loader/src/main/java/ru/croc/ctp/jxfw/wc/web/bootloader/ScriptMatcher.java:17— ScriptMatcher.isMatch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XfwXslfoReport.insertScripts (cognitive 16) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/impl/XfwXslfoReport.java:455— XfwXslfoReport.insertScripts has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (5 pts), match/switch 1 (5 pts), error handling 1 (4 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LayoutColumn.resetTotals (cognitive 16) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:597— LayoutColumn.resetTotals has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (15 pts), match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java holds 10 of the 121 methods over the threshold — including the worst — and 711 of the 2284 points over it (31%), 4.8× the next-largest file (jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java at 147). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
GenericLayoutManager.distributeHeightGap (cognitive 16) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/layout/layoutmanager/GenericLayoutManager.java:378— GenericLayoutManager.distributeHeightGap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 1 (3 pts), loops 2, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (GenericLayoutManager.distributeWidthGap) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
GenericLayoutManager.distributeWidthGap (cognitive 16) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/layout/layoutmanager/GenericLayoutManager.java:323— GenericLayoutManager.distributeWidthGap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 1 (3 pts), loops 2, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (GenericLayoutManager.distributeHeightGap) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
AreaTreeBuilder.checkAreaProgressionDirection (cognitive 16) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/tree/AreaTreeBuilder.java:1346— AreaTreeBuilder.checkAreaProgressionDirection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InlineAreasExcelRenderer.doRenderInlineAreas (cognitive 16) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/rendering/excel/InlineAreasExcelRenderer.java:168— InlineAreasExcelRenderer.doRenderInlineAreas has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WordRenderer.addRegion (cognitive 16) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1522— WordRenderer.addRegion has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (16 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PredicateComposer.createMultiplyExpressions (cognitive 16) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/facade/webclient/PredicateComposer.java:236— PredicateComposer.createMultiplyExpressions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QTupleDataSourceResultSerializer.serialize (cognitive 16) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/facade/webclient/QTupleDataSourceResultSerializer.java:34— QTupleDataSourceResultSerializer.serialize has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Near-duplicate member pair (36 shared lines) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/solr/ToServiceGeneratorSolr.java:275— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/solr/ToServiceGeneratorSolr.java:275-360 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:412-464 — These two members are variants of one another: 36 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (96 corresponding lines) · ×1
Edited copy of a member (96 corresponding lines) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1473— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1473-1568 | jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1187-1282 — These two members are one piece of code written twice and then edited apart: 96 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (84–86 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:652— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:652-737 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:711-794 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:652` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (68 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:967— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:967-1034 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1055-1122 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (54 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1189— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1189-1242 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1475-1528 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1189` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (41 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java:301— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java:301-341 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/FoFont.java:218-258 — before extracting anything, compare `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java` and `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/FoFont.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/foproperty/font/FoFont.java:301` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25–35 lines × 3) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java:98— jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java:98-122 | jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImplWithXmlns.java:123-147 | scriptgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/solr/MapFieldToSolr.java:21-55 — before extracting anything, compare `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java` and `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImplWithXmlns.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 80 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/service/TransferToTransformerImpl.java:98` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (33 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java:63— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java:63-95 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/jpa/ToServiceGeneratorJpa.java:68-100 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/jpa/ToServiceGeneratorJpa.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (31 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1516— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:1516-1546 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1802-1832 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (28 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java:106— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java:106-133 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/jpa/ToServiceGeneratorJpa.java:117-144 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/jpa/TransferToServiceGeneratorJpa.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/jpa/ToServiceGeneratorJpa.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (24–25 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:294— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:294-318 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:298-321 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:294` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:297` calls `addMethod`, `createEqualsObjectMethod`, `build` and `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:292` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (24 lines × 3) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2419— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2419-2442 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2500-2523 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2638-2661 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2524` calls `getLayoutTable`, `getCurrentRow`, `getCurrentCell` and `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2444` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (22 lines × 2) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1376— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1376-1397 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1399-1420 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20–22 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2081— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2081-2102 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2230-2249 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2081` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (20–21 lines × 2) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1235— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1235-1255 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1260-1279 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:1235` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (17–18 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/attribute/AttributeParser.java:185— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/attribute/AttributeParser.java:185-202 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/tree/attribute/AttributeParser.java:228-244 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/processing/attribute/AttributeParser.java:185` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 4) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2422— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2422-2438 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2503-2519 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2641-2657 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2760-2776 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2524` calls `getLayoutTable`, `getCurrentRow`, `getCurrentCell` and `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2444` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16–17 lines × 2) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:534— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:534-550 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:544-559 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:534` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:543` calls `addStatement` and `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:534` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (15–16 lines × 4) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2350— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2350-2365 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2394-2408 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2574-2589 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2697-2712 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2350` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 3) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:441— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:441-456 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:449-464 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/solr/ToServiceGeneratorSolr.java:345-360 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:441` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 4) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/dialect/XfwH2Dialect.java:59— jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/dialect/XfwH2Dialect.java:59-73 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/dialect/XfwMySqlDialect.java:56-70 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/dialect/XfwOracle10gDialect.java:56-70 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/dialect/XfwPostgreSql9Dialect.java:56-70 — before extracting anything, compare `jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/dialect/XfwH2Dialect.java` and `jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/hibernate/dialect/XfwMySqlDialect.java` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12–15 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2152— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2152-2166 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2172-2183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2152` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/rendering/excel/ExcelRenderer.java:600— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/rendering/excel/ExcelRenderer.java:600-614 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/rendering/excel/ExcelRenderer.java:661-674 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/rendering/excel/ExcelRenderer.java:600` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 3) jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:422— jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:422-435 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java:430-443 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/solr/ToServiceGeneratorSolr.java:326-339 — before extracting anything, compare `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java` and `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ToServiceGenerator.java` as WHOLE FILES: this scan already matched 41 separate duplicated blocks between them, totalling at least 727 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer-facade-gen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/transfer/TransferToServiceGenerator.java:422` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–13 lines × 5) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2419— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2419-2430 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2500-2511 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2614-2626 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2638-2649 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2760-2768 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:2419` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11 lines × 3) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ControllerGenerationUtils.java:171— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ControllerGenerationUtils.java:171-181 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:568-579 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:648-659 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/ControllerGenerationUtils.java:171` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10–11 lines × 3) jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:141— jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:141-150 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:199-208 | jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:228-238 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:151` calls `setConstraint` and `jxfw-jpa-runtime/src/main/java/ru/croc/ctp/jxfw/jpa/exception/impl/H2DbExceptionParser.java:209` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9–11 lines × 2) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/list/ListItemArea.java:60— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/list/ListItemArea.java:60-68 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/list/ListItemArea.java:79-89 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/excel/core/element/area/list/ListItemArea.java:60` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 3) jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:109— jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:109-118 | jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:177-187 | jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:239-248 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:174` calls `addFileDownLoadCookieAndHeader`, `getExtension` and `jxfw-reporting-birt/src/main/java/ru/croc/ctp/jxfw/reporting/birt/impl/BirtReportServiceImpl.java:235` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7–8 lines × 2) wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:182— wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:182-188 | wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:270-277 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `wcgen-maven-plugin/src/main/java/ru/croc/ctp/jxfw/facade/WebClientControllerCreator.java:182` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6–7 lines × 2) jxfw-cass-runtime/src/main/java/ru/croc/ctp/jxfw/cass/facade/webclient/SelectComposer.java:318— jxfw-cass-runtime/src/main/java/ru/croc/ctp/jxfw/cass/facade/webclient/SelectComposer.java:318-323 | jxfw-cass-runtime/src/main/java/ru/croc/ctp/jxfw/cass/facade/webclient/SelectComposer.java:344-350 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-cass-runtime/src/main/java/ru/croc/ctp/jxfw/cass/facade/webclient/SelectComposer.java:318` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:630— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:630-635 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1180-1185 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1208-1213 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `area` to `InlineArea` in one and `PageNumberArea` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:1187` calls `insertField` and `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/rendering/WordRenderer.java:637` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (3–5 lines × 3) jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:1345— jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:1345-1347 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:1354-1358 | jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:1368-1373 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-reporting-xsl-fo/src/main/java/ru/croc/ctp/jxfw/reporting/xslfo/layouts/TableLayout.java:1345` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 3) jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/datasource/DomainObjectDataSourceResult.java:33— jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/datasource/DomainObjectDataSourceResult.java:33-66 | jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/datasource/GeneralDataSourceResult.java:32-54 | jxfw-core-runtime/src/main/java/ru/croc/ctp/jxfw/core/datasource/PojoDataSourceResult.java:32-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `data` to `Iterable<DomainObject<? extends Serializable>>` in one and `Iterable<T>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (52 lines × 2) REDACTED:1— REDACTED:1-52 | REDACTED:1-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (93 lines × 2) jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/config/JsonXfwTransferConfig.java:1— jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/config/JsonXfwTransferConfig.java:1-95 | jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/config/XmlXfwTransferConfig.java:1-93 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `jxfw-transfer/src/main/java/ru/croc/ctp/jxfw/transfer/config/JsonXfwTransferConfig.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Coverage not measured — no coverage collector is wired up — Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect.
Documentation: no usage examples README.md— There are no usage examples showing how to invoke jXFW or what output it produces. Write a short 'how to run it' example with input and expected output.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
Thin README — The root README is 38 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, it found no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No SAST — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1036 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
Skipped (documented): toStringOfReadSessionEventTest jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/load/events/EventsTest.java:27— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
Skipped (documented): httpResource jxfw-core-runtime/src/test/java/ru/croc/ctp/jxfw/core/reporting/impl/XfwResourceLoaderTest.java:15— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
Skipped (documented): endElementThroughReaderApi jxfw-reporting-xsl-fo/src/test/java/ru/croc/ctp/jxfw/reporting/xslfo/renderer/word/processing/XslFoTreeBuilderTest.java:19— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a0c09f-1736-7dcc-a9da-a21a822d3555 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 9 · Warnings: 495 · Recommendations: 14 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 20-09-2026 @ 21:00 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.