Public report — stalactite, published 29 Jul 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
215findings with an exact file:lineof 221 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
20/94dimensions across the health lenses78650 LoC — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
codefilarete/stalactite is sound in substance but carries real gaps (55%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Security (97%) — its security and compliance posture is in good shape. Architecture (97%) is solid too.
The area that most needs attention is Readiness (26%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade.
Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); SAST step to CI running what this repository's stack ships (Security & performance tooling); Keep a changelog (e.g. Keep-a-Changelog) recording what shipped… (Release Hygiene).
For scale: Medium (~78,650 production lines); rebuilding it from scratch would take roughly ~0.9 person-years (~1–2 engineers). Approximate, ±~30%.
Encouragingly, the gaps are in documentation and release process — not in the code's correctness, structure or security, which are strong. They're low-risk to close, and doing so would lift the grade without re-engineering anything that already works.
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.
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.8× (at 55% quality) — the last 20% of quality is most of the work
Size & shape
Medium · 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 ~€140,000 to rebuild). Its weakest lens is Readiness at 26% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 0.8× 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
Add a CI workflow that builds and runs the test suite on every push/PR.
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.
Value concentrated against a weak lens · High · Value at risk
This is a Medium asset (~0.9 person-years to rebuild), and its weakest lens is Readiness at 26%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Add a CI workflow that builds and runs the test suite on every push/PR. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a CI workflow that builds and runs the test suite on every push/PR.
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
1
Medium
Roadmap
First, establish a continuous integration workflow that builds and tests every change to ensure immediate feedback. Next, integrate static analysis tools to automatically fail the build on security or performance regressions. Then, maintain a changelog to clearly document what is shipped in each release. Additionally, update the README to include clear instructions for running the test suite. Finally, begin recording significant architectural decisions and their rationale to preserve institutional knowledge.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a CI workflow that builds and runs the test suite on every push/PR.
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.
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. 18 of 20 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.4 — 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 — 20 dimensions across the health lenses
D1D2D3D4D13D15D16D19D21D28D29D34D35M1M2M3M4P1P3P6
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, 215 of 221 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.
D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
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 (jscpd) — 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.
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.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
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.
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").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
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.
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.
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 (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These 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.
Resolve the 1 AbstractDerivedQuery.convertToCriterion (cyclomatic 41) finding(s) in Cyclomatic Complexity — start with AbstractDerivedQuery.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 OneToManyOwnedByTargetHelper.determineForeignKeyColumns (cyclomatic 16) finding(s) in Cyclomatic Complexity — start with OneToManyMetadataResolver.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 OneToManyWithMappedAssociationConfigurer.determineForeignKeyColumns… finding(s) in Cyclomatic Complexity — start with OneToManyWithMappedAssociationConfigurer.java. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.
+ 13 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 ManyToManyMetadataResolver.buildReverseCombiner (cognitive 31) finding(s) in Cognitive Complexity — start with ManyToManyMetadataResolver.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 OneToManyMetadataResolver.resolve (cognitive 31) finding(s) in Cognitive Complexity — start with OneToManyMetadataResolver.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 ManyToManyWithAssociationTableConfigurer.buildReverseCombiner (cognitive… finding(s) in Cognitive Complexity — start with ManyToManyRelationConfigurer.java. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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 Classes9.1 / 10Exemplary✓ 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.
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.
+ 24 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 21 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with DeleteCommandBuilder.java (2), PropertyMappingResolver.java (2), Column.java. — One of this dimension's main actionable groups (21 warning-level).
Resolve the 20 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with OneToManyMetadataResolver.java (2), ElementCollectionLoader.java (2), ManyToOneCycleLoader.java. — One of this dimension's main actionable groups (20 warning-level).
Resolve the 18 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with DeleteCommandBuilder.java (2), OneToOneOwnedByTargetEngine.java (2), DerbyTypeMapping.java. — One of this dimension's main actionable groups (18 warning-level).
Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. 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.
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.
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor5.6 / 10Adequate✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
232 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/FluentEntityMappingConfigurationSupport.java.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_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.
Stalactite's documentation is strong and well-structured: a README with an engaging philosophy section ('embraces Clean and Hexagonal Architectures') plus a direct example usage that clips mid-sentence (and the full outline), plus dedicated technical docs covering class design, a SQL module explaining JDBC-layer features like result iteration and transaction listening, an ORM adapter directory describing each supported database's pom submodules, and a core module with detailed persistence strategies and query-building examples. The absence of architecture/design docs is notable but not critical given the README alone already gives a clear picture.
The adaptation layer for PostgreSQL is described only in a truncated section ('Specifies adhoc PostgreSQL SQL types...') and no further details on how it maps JDBC types to the database schema.sql-adapter/sql-postgresql-adapter/README.md
What to do
Resolve the 1 The adaptation layer for PostgreSQL is described only in a truncated… 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.
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: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
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).
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
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; coupling through a build step, config, or non-source file isn't seen.
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.
565 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
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 21 of 35 project(s) that lack one — worth up to 1.2 pts.
Review the README against recent changes; refresh the parts that drifted.
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 gates0.0 / 10Critical✓ 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.
No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
Add a CI workflow that builds and runs the test suite on every push/PR.
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 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 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 included — 74 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
AX10 Code composition — not assessed — code composition is computed by ROLE over the .NET document set and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over the .NET project-reference graph and none was loaded for this repository, because it is written in another language or the solution 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 the .NET project-reference graph and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
AX5 Architecture & structure — not assessed — architecture style/structure is computed from the .NET project graph (projects, types, namespaces) and no such graph was loaded for this repository, because it is written in another language or the solution 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 the .NET type surface and none was loaded for this repository, because it is written in another language or the solution 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 the .NET project graph (which projects are test projects, and what they reference) and no such graph was loaded for this repository, because it is written in another language or the solution 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 — no data
C1 Data Protection — Not assessed: these personal data controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom 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 C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom 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.
C3 Audit Trail — Not assessed: these audit controls are read from C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom 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 C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom 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 C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom 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.
D10 Test Quality — ~59595 lines of test source are present (.java) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included
D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
D14 License Compliance — Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (a Maven POM), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
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.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No exposed public API
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 namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["Acme.Billing"]`, `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 — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Maven POM — not scanned yet) — where an OSV-supported manifest exists, dependency vulnerabilities for this repository are reported under D38 instead.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.
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.
D38 OSV Dependency Vulnerabilities — Scanner failed to run — not a clean result
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.
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 C#/VB 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 dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
D9 Test Distribution — Test source is present (.java) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 282 value object(s); a Domain/Aggregates/ValueObjects layer
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
GD1 Unfinished & placeholder code — no source files
IC1 Incompleteness & stubs — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — no CI workflow found
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.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
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`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, 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 C# source (attributes, middleware, entity/column names, guard methods) and no C# source was loaded for this repository — because it is written in another language, or the solution failed to load. Absence of a .NET idiom 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 are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
X2 Cancellation propagation — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
X3 Exception handling — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
X4 Structured logging — not analysed — these correctness checks are read from C# source and none was loaded for this repository, because it is written in another language or the solution 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 are read from C# source and none was loaded for this repository, because it is written in another language or the solution failed to load. This is a gap in the analyzer, not a finding about this repository
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.
Duplicated block (7 lines × 2) core/src/main/java/org/codefilarete/stalactite/sql/ddl/structure/Column.java:40— core/src/main/java/org/codefilarete/stalactite/sql/ddl/structure/Column.java:40-46 | core/src/main/java/org/codefilarete/stalactite/sql/ddl/structure/Column.java:50-56 — 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 (7 lines × 2) core/src/main/java/org/codefilarete/stalactite/sql/order/DeleteCommandBuilder.java:79— core/src/main/java/org/codefilarete/stalactite/sql/order/DeleteCommandBuilder.java:79-85 | core/src/main/java/org/codefilarete/stalactite/sql/order/UpdateCommandBuilder.java:72-78 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (7 lines × 2) core/src/main/java/org/codefilarete/stalactite/sql/order/DeleteCommandBuilder.java:135— core/src/main/java/org/codefilarete/stalactite/sql/order/DeleteCommandBuilder.java:135-141 | core/src/main/java/org/codefilarete/stalactite/sql/order/UpdateCommandBuilder.java:174-180 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/load/JoinTableRootJoinNode.java:62— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/load/JoinTableRootJoinNode.java:62-68 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/load/TablePerClassRootJoinNode.java:65-71 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/cycle/ManyToOneCycleLoader.java:49— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/cycle/ManyToOneCycleLoader.java:49-55 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/cycle/OneToOneCycleLoader.java:49-55 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithMappedAssociationEngine.java:407— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithMappedAssociationEngine.java:407-413 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyWithMappedAssociationEngine.java:323-329 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/singletable/SingleTablePolymorphismEntityFinder.java:182— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/singletable/SingleTablePolymorphismEntityFinder.java:182-188 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/tableperclass/TablePerClassPolymorphismEntityFinder.java:278-284 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/cascade/AfterInsertCollectionCascader.java:51— orm/src/main/java/org/codefilarete/stalactite/engine/cascade/AfterInsertCollectionCascader.java:51-57 | orm/src/main/java/org/codefilarete/stalactite/engine/cascade/BeforeInsertCollectionCascader.java:44-50 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:278— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:278-284 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PropertyMappingResolver.java:242-248 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/IdentifierManagerStep.java:115— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/IdentifierManagerStep.java:115-121 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/IdentifierMappingBuilder.java:105-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToManyMetadataResolver.java:322— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToManyMetadataResolver.java:322-328 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyAssociationConfiguration.java:139-145 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PropertyMappingResolver.java:73— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PropertyMappingResolver.java:73-79 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PropertyMappingResolver.java:99-105 — 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 (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PropertyMappingResolver.java:82— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PropertyMappingResolver.java:82-88 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PropertyMappingResolver.java:108-114 — 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 (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/EntityDecoratedEmbeddableConfigurationSupport.java:305— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/EntityDecoratedEmbeddableConfigurationSupport.java:305-311 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/EntityDecoratedEmbeddableConfigurationSupport.java:337-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.
Duplicated block (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/FluentEntityMappingConfigurationSupport.java:517— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/FluentEntityMappingConfigurationSupport.java:517-523 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/FluentEntityMappingConfigurationSupport.java:561-567 — 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 (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyAndValueMapRelationConfigurer.java:302— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyAndValueMapRelationConfigurer.java:302-308 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyMapRelationConfigurer.java:306-312 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/elementcollection/ElementCollectionLoader.java:115— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/elementcollection/ElementCollectionLoader.java:115-121 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/MapEntryLoader.java:126-132 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/FluentSubEntityMappingConfigurationSupport.java:169— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/FluentSubEntityMappingConfigurationSupport.java:169-176 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/FluentSubEntityMappingConfigurationSupport.java:181-187 — 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 (7 lines × 2) core/src/main/java/org/codefilarete/stalactite/engine/PersistExecutor.java:103— core/src/main/java/org/codefilarete/stalactite/engine/PersistExecutor.java:103-109 | core/src/main/java/org/codefilarete/stalactite/engine/PersistExecutor.java:155-161 — 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 (7 lines × 2) core/src/main/java/org/codefilarete/stalactite/mapping/EmbeddedClassMapping.java:301— core/src/main/java/org/codefilarete/stalactite/mapping/EmbeddedClassMapping.java:301-307 | core/src/main/java/org/codefilarete/stalactite/mapping/ZonedDateTimeMapping.java:118-124 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (7 lines × 2) orm/src/main/java/org/codefilarete/stalactite/dsl/naming/ElementCollectionTableNamingStrategy.java:38— orm/src/main/java/org/codefilarete/stalactite/dsl/naming/ElementCollectionTableNamingStrategy.java:38-44 | orm/src/main/java/org/codefilarete/stalactite/dsl/naming/MapTableNamingStrategy.java:53-59 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/cycle/ManyToOneCycleLoader.java:36— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/cycle/ManyToOneCycleLoader.java:36-44 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/cycle/OneToOneCycleLoader.java:36-44 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/jointable/JoinTablePolymorphismPersister.java:192— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/jointable/JoinTablePolymorphismPersister.java:192-200 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/singletable/SingleTablePolymorphismPersister.java:197-205 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedBySourceEngine.java:66— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedBySourceEngine.java:66-74 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetoone/OneToOneOwnedBySourceEngine.java:67-75 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/projection/ProjectionQueryCriteriaSupport.java:127— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/projection/ProjectionQueryCriteriaSupport.java:127-135 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/query/EntityQueryCriteriaSupport.java:169-177 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/SimpleRelationalEntityPersister.java:219— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/SimpleRelationalEntityPersister.java:219-227 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/SimpleRelationalEntityPersister.java:266-274 — 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 (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:371— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:371-379 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PropertyMappingResolver.java:346-354 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/IdentificationStep.java:76— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/IdentificationStep.java:76-84 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/IdentifierMappingBuilder.java:86-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/MainPersisterStep.java:239— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/MainPersisterStep.java:239-247 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/VersioningStep.java:47-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ElementCollectionMetadataResolver.java:214— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ElementCollectionMetadataResolver.java:214-222 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/ElementCollectionRelationConfigurer.java:179-187 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java:117— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java:117-125 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java:149-157 — 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 (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java:249— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java:249-257 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetomany/OneToManyWithMappedAssociationConfigurer.java:142-150 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyRelation.java:216— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyRelation.java:216-224 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetomany/OneToManyRelation.java:307-315 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyRelationConfigurer.java:369— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyRelationConfigurer.java:369-377 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetomany/OneToManyWithAssociationTableConfigurer.java:180-188 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytoone/ManyToOneConfigurer.java:323— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytoone/ManyToOneConfigurer.java:323-331 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetoone/OneToOneOwnedBySourceConfigurer.java:111-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyAndValueMapRelationConfigurer.java:309— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyAndValueMapRelationConfigurer.java:309-317 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsValueMapRelationConfigurer.java:305-313 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsValueMapRelationConfigurer.java:218— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsValueMapRelationConfigurer.java:218-226 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/MapRelationConfigurer.java:174-182 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/elementcollection/ElementCollectionLoader.java:127— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/elementcollection/ElementCollectionLoader.java:127-135 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/MapEntryLoader.java:138-146 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/elementcollection/ElementCollectionLoader.java:164— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/elementcollection/ElementCollectionLoader.java:164-172 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/MapEntryLoader.java:175-183 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (9 lines × 2) core/src/main/java/org/codefilarete/stalactite/query/builder/ExpandableSQLAppender.java:119— core/src/main/java/org/codefilarete/stalactite/query/builder/ExpandableSQLAppender.java:119-127 | core/src/main/java/org/codefilarete/stalactite/query/builder/PreparedSQLAppender.java:69-77 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (9 lines × 2) spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/domain/DomainEntityQueryExecutor.java:73— spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/domain/DomainEntityQueryExecutor.java:73-81 | spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/projection/ProjectionQueryExecutor.java:86-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 2) sql-adapter/sql-derby-adapter/src/main/java/org/codefilarete/stalactite/sql/derby/statement/binder/DerbyTypeMapping.java:17— sql-adapter/sql-derby-adapter/src/main/java/org/codefilarete/stalactite/sql/derby/statement/binder/DerbyTypeMapping.java:17-24 | sql-adapter/sql-hsqldb-adapter/src/main/java/org/codefilarete/stalactite/sql/hsqldb/statement/binder/HSQLDBTypeMapping.java:17-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 2) core/src/main/java/org/codefilarete/stalactite/sql/order/DeleteCommandBuilder.java:113— core/src/main/java/org/codefilarete/stalactite/sql/order/DeleteCommandBuilder.java:113-120 | core/src/main/java/org/codefilarete/stalactite/sql/order/UpdateCommandBuilder.java:147-154 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (8 lines × 2) core/src/main/java/org/codefilarete/stalactite/sql/order/DeleteCommandBuilder.java:189— core/src/main/java/org/codefilarete/stalactite/sql/order/DeleteCommandBuilder.java:189-196 | core/src/main/java/org/codefilarete/stalactite/sql/order/UpdateCommandBuilder.java:233-240 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (8 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:249— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:249-256 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:141-148 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedBySourceEngine.java:107— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedBySourceEngine.java:107-114 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetoone/OneToOneOwnedBySourceEngine.java:108-115 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:240— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:240-247 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetoone/OneToOneOwnedByTargetEngine.java:241-248 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:325— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:325-332 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetoone/OneToOneOwnedByTargetEngine.java:326-333 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/projection/ProjectionQueryPageSupport.java:102— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/projection/ProjectionQueryPageSupport.java:102-109 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/query/EntityQueryCriteriaSupport.java:313-320 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/singletable/SingleTablePolymorphismEntityFinder.java:146— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/singletable/SingleTablePolymorphismEntityFinder.java:146-153 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/tableperclass/TablePerClassPolymorphismEntityFinder.java:230-238 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/singletable/SingleTablePolymorphismPersister.java:252— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/singletable/SingleTablePolymorphismPersister.java:252-259 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/singletable/SingleTablePolymorphismPersister.java:293-301 — 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) core/src/main/java/org/codefilarete/stalactite/engine/runtime/InsertExecutor.java:56— core/src/main/java/org/codefilarete/stalactite/engine/runtime/InsertExecutor.java:56-63 | core/src/main/java/org/codefilarete/stalactite/engine/runtime/UpdateExecutor.java:58-65 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (8 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:90— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:90-97 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:106-113 — 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) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java:216— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java:216-223 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetomany/OneToManyWithMappedAssociationConfigurer.java:91-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/EntityDecoratedEmbeddableConfigurationSupport.java:350— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/EntityDecoratedEmbeddableConfigurationSupport.java:350-357 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/EntityDecoratedEmbeddableConfigurationSupport.java:438-445 — 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) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytoone/ManyToOneConfigurer.java:334— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytoone/ManyToOneConfigurer.java:334-341 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetoone/OneToOneOwnedBySourceConfigurer.java:122-129 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetomany/OneToManyWithMappedAssociationConfigurer.java:100— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetomany/OneToManyWithMappedAssociationConfigurer.java:100-107 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetomany/OneToManyWithMappedAssociationConfigurer.java:121-128 — 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) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/SkeletonAggregateResolver.java:217— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/SkeletonAggregateResolver.java:217-224 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/SkeletonAggregateResolver.java:267-274 — 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) orm/src/main/java/org/codefilarete/stalactite/dsl/naming/AssociationTableNamingStrategy.java:136— orm/src/main/java/org/codefilarete/stalactite/dsl/naming/AssociationTableNamingStrategy.java:136-143 | orm/src/main/java/org/codefilarete/stalactite/dsl/naming/AssociationTableNamingStrategy.java:179-186 — 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) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/manytoone/ManyToOneEngine.java:119— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/manytoone/ManyToOneEngine.java:119-124 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytoone/ManyToOneEngine.java:120-125 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (6 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/IndexedMappedManyRelationDescriptor.java:90— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/IndexedMappedManyRelationDescriptor.java:90-95 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/IndexedMappedManyRelationDescriptor.java:90-95 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (6 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:361— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:361-366 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:253-258 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (6 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:369— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:369-374 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetoone/OneToOneOwnedByTargetEngine.java:370-375 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (6 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/AbstractPolymorphicEntityFinder.java:162— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/AbstractPolymorphicEntityFinder.java:162-167 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/RelationalEntityFinder.java:251-256 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (6 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/SimpleRelationalEntityPersister.java:95— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/SimpleRelationalEntityPersister.java:95-100 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/SimpleRelationalEntityPersister.java:108-113 — 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) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:504— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:504-509 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:512-517 — 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) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:549— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:549-554 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PropertyMappingResolver.java:379-384 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (6 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/IdentifierManagerStep.java:109— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/IdentifierManagerStep.java:109-114 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/IdentifierMappingBuilder.java:153-158 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (6 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/PrimaryKeyStep.java:46— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/PrimaryKeyStep.java:46-51 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PrimaryKeyResolver.java:40-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (6 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PolymorphismMetadataResolver.java:71— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PolymorphismMetadataResolver.java:71-77 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PolymorphismMetadataResolver.java:98-103 — 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) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/ElementCollectionRelationConfigurer.java:161— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/ElementCollectionRelationConfigurer.java:161-166 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/ElementCollectionRelationConfigurer.java:203-209 — 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) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyAndValueMapRelationConfigurer.java:355— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyAndValueMapRelationConfigurer.java:355-360 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyMapRelationConfigurer.java:352-357 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (6 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyAndValueMapRelationConfigurer.java:363— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyAndValueMapRelationConfigurer.java:363-370 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsValueMapRelationConfigurer.java:351-356 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (6 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/MapUpdater.java:100— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/MapUpdater.java:100-105 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/MapUpdater.java:103-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (6 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/MapUpdater.java:176— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/MapUpdater.java:176-181 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/MapUpdater.java:179-184 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (6 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/ManyToManyResolver.java:104— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/ManyToManyResolver.java:104-111 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyResolver.java:136-141 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (6 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/ManyToManyResolver.java:145— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/ManyToManyResolver.java:145-153 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyResolver.java:170-175 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (11 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingConfiguration.java:127— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingConfiguration.java:127-137 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingConfiguration.java:203-213 — 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 (11 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToManyMetadataResolver.java:263— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToManyMetadataResolver.java:263-273 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyRelationConfigurer.java:208-218 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (11 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToOneMetadataResolver.java:173— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToOneMetadataResolver.java:173-183 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToOneMetadataResolver.java:220-230 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (11 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToOneMetadataResolver.java:140— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToOneMetadataResolver.java:140-150 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetoone/OneToOneOwnedByTargetConfigurer.java:186-196 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (11 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyAssociationConfiguration.java:143— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyAssociationConfiguration.java:143-153 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytoone/ManyToOneRelation.java:150-160 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (11 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytoone/ManyToOneRelationConfigurer.java:65— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytoone/ManyToOneRelationConfigurer.java:65-75 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetoone/OneToOneRelationConfigurer.java:75-85 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (11 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyMapRelationConfigurer.java:207— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyMapRelationConfigurer.java:207-217 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsValueMapRelationConfigurer.java:206-216 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (11 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetoone/OrphanRemovalOnUpdate.java:27— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetoone/OrphanRemovalOnUpdate.java:27-37 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/OrphanRemovalOnUpdate.java:27-37 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (11 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/AggregateManyToManyAppender.java:155— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/AggregateManyToManyAppender.java:155-166 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/AggregateOneToManyWithAssociationTableAppender.java:62-72 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (11 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/AggregateMapAppender.java:240— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/AggregateMapAppender.java:240-250 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/AggregateMapAppender.java:277-287 — 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 (11 lines × 2) core/src/main/java/org/codefilarete/stalactite/mapping/ColumnedCollectionMapping.java:116— core/src/main/java/org/codefilarete/stalactite/mapping/ColumnedCollectionMapping.java:116-127 | core/src/main/java/org/codefilarete/stalactite/mapping/ColumnedMapMapping.java:115-125 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (11 lines × 2) spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/execution/reduce/QueryResultStreamer.java:52— spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/execution/reduce/QueryResultStreamer.java:52-62 | spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/execution/reduce/SliceResultWindower.java:40-50 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/load/JoinTablePolymorphicRelationJoinNode.java:99— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/load/JoinTablePolymorphicRelationJoinNode.java:99-108 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/load/TablePerClassPolymorphicRelationJoinNode.java:160-173 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/manytoone/ManyToOneEngine.java:51— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/manytoone/ManyToOneEngine.java:51-60 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytoone/ManyToOneEngine.java:52-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/IndexedAssociationTableManyRelationDescriptor.java:128— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/IndexedAssociationTableManyRelationDescriptor.java:128-137 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/IndexedAssociationTableManyRelationDescriptor.java:128-137 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/IndexedMappedManyRelationDescriptor.java:124— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/IndexedMappedManyRelationDescriptor.java:124-133 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/IndexedMappedManyRelationDescriptor.java:124-133 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithAssociationTableEngine.java:211— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithAssociationTableEngine.java:211-220 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyWithAssociationTableEngine.java:152-161 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithAssociationTableEngine.java:231— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithAssociationTableEngine.java:231-240 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyWithAssociationTableEngine.java:172-181 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedBySourceEngine.java:41— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedBySourceEngine.java:41-50 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetoone/OneToOneOwnedBySourceEngine.java:42-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:148— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:148-157 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetoone/OneToOneOwnedByTargetEngine.java:149-158 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:329— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:329-338 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PropertyMappingResolver.java:306-315 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetoone/OneToOneConfigurerTemplate.java:61— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetoone/OneToOneConfigurerTemplate.java:61-70 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetoone/OneToOneConfigurerTemplate.java:79-88 — 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 (10 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/AggregateOneToManyAppender.java:49— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/AggregateOneToManyAppender.java:49-58 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/AggregateOneToManyWithMappedAssociationAppender.java:90-99 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/execution/reduce/QueryResultStreamer.java:33— spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/execution/reduce/QueryResultStreamer.java:33-42 | spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/execution/reduce/SliceResultWindower.java:22-31 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (13 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/cycle/ManyToManyCycleLoader.java:46— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/cycle/ManyToManyCycleLoader.java:46-58 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/cycle/OneToManyCycleLoader.java:46-58 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (13 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/jointable/JoinTablePolymorphismPersister.java:252— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/jointable/JoinTablePolymorphismPersister.java:252-264 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/jointable/JoinTablePolymorphismPersister.java:301-313 — 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) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:295— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:295-307 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:187-199 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (13 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:318— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:318-330 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:210-222 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (13 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:257— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:257-269 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetoone/OneToOneOwnedByTargetEngine.java:258-270 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (13 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ElementCollectionMetadataResolver.java:226— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ElementCollectionMetadataResolver.java:226-238 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/ElementCollectionRelationConfigurer.java:191-203 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (13 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToOneMetadataResolver.java:247— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToOneMetadataResolver.java:247-259 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytoone/ManyToOneConfigurer.java:157-169 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (13 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/EntityDecoratedEmbeddableConfigurationSupport.java:125— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/EntityDecoratedEmbeddableConfigurationSupport.java:125-137 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/FluentSubEntityMappingConfigurationSupport.java:623-635 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (13 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/FluentEntityMappingConfigurationSupport.java:1174— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/FluentEntityMappingConfigurationSupport.java:1174-1186 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/FluentSubEntityMappingConfigurationSupport.java:496-508 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (13 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyMapRelationConfigurer.java:120— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyMapRelationConfigurer.java:120-132 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsValueMapRelationConfigurer.java:119-131 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (13 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/AggregateManyToManyAppender.java:89— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/AggregateManyToManyAppender.java:89-101 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/AggregateOneToManyWithMappedAssociationAppender.java:86-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Change coupling: BeanRepositoryQuery.java ↔ DomainEntityNativeQueryExecutor.java spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/bean/BeanRepositoryQuery.java— `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/bean/BeanRepositoryQuery.java` and `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/nativ/DomainEntityNativeQueryExecutor.java` change together 70% of the time (7 of the 10 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: PartTreeStalactiteDelete.java ↔ PartTreeStalactiteProjection.java spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/domain/PartTreeStalactiteDelete.java— `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/domain/PartTreeStalactiteDelete.java` and `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/projection/PartTreeStalactiteProjection.java` change together 70% of the time (7 of the 10 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: AbstractDerivedQuery.java ↔ PartTreeStalactiteProjection.java spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/derivation/AbstractDerivedQuery.java— `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/derivation/AbstractDerivedQuery.java` and `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/projection/PartTreeStalactiteProjection.java` change together 62% of the time (10 of the 16 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: AbstractRepositoryQuery.java ↔ TupleNativeQueryExecutor.java spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/execution/AbstractRepositoryQuery.java— `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/execution/AbstractRepositoryQuery.java` and `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/nativ/TupleNativeQueryExecutor.java` change together 62% of the time (8 of the 13 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: AbstractRepositoryQuery.java ↔ DomainEntityNativeQueryExecutor.java spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/execution/AbstractRepositoryQuery.java— `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/execution/AbstractRepositoryQuery.java` and `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/nativ/DomainEntityNativeQueryExecutor.java` change together 60% of the time (6 of the 10 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: FluentEntityMappingBuilder.java ↔ MapRelation.java orm/src/main/java/org/codefilarete/stalactite/dsl/entity/FluentEntityMappingBuilder.java— `orm/src/main/java/org/codefilarete/stalactite/dsl/entity/FluentEntityMappingBuilder.java` and `orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/MapRelation.java` change together 60% of the time (6 of the 10 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: CompositeKeyMappingConfiguration.java ↔ FluentEmbeddableMappingConfigurationSupport.java orm/src/main/java/org/codefilarete/stalactite/dsl/key/CompositeKeyMappingConfiguration.java— `orm/src/main/java/org/codefilarete/stalactite/dsl/key/CompositeKeyMappingConfiguration.java` and `orm/src/main/java/org/codefilarete/stalactite/engine/configurer/embeddable/FluentEmbeddableMappingConfigurationSupport.java` change together 60% of the time (6 of the 10 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: DomainEntityNativeQueryExecutor.java ↔ PartTreeStalactiteProjection.java spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/nativ/DomainEntityNativeQueryExecutor.java— `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/nativ/DomainEntityNativeQueryExecutor.java` and `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/projection/PartTreeStalactiteProjection.java` change together 60% of the time (6 of the 10 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: DatabaseCrudOperations.java ↔ Update.java core/src/main/java/org/codefilarete/stalactite/engine/crud/DatabaseCrudOperations.java— `core/src/main/java/org/codefilarete/stalactite/engine/crud/DatabaseCrudOperations.java` and `core/src/main/java/org/codefilarete/stalactite/sql/order/Update.java` change together 55% of the time (6 of the 11 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Change coupling: BeanRepositoryQuery.java ↔ TupleNativeQueryExecutor.java spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/bean/BeanRepositoryQuery.java— `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/bean/BeanRepositoryQuery.java` and `spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/nativ/TupleNativeQueryExecutor.java` change together 54% of the time (7 of the 13 commits that touched the less-changed of the two, renames followed) with no explicit dependency — a hidden/logical coupling. If they belong together, co-locate them; if not, break the coupling.
Duplicated block (14 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithMappedAssociationEngine.java:235— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithMappedAssociationEngine.java:235-248 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyWithMappedAssociationEngine.java:188-201 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (14 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:350— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java:350-363 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/PropertyMappingResolver.java:326-339 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (14 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyRelationConfigurer.java:300— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyRelationConfigurer.java:300-314 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetomany/OneToManyWithAssociationTableConfigurer.java:110-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (14 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytoone/ManyToOneConfigurer.java:300— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytoone/ManyToOneConfigurer.java:300-313 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetoone/OneToOneConfigurerTemplate.java:170-183 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (14 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/elementcollection/ElementCollectionLoader.java:100— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/elementcollection/ElementCollectionLoader.java:100-113 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/MapEntryLoader.java:111-124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (14 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/ManyToManyResolver.java:119— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/ManyToManyResolver.java:119-132 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyResolver.java:149-162 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (14 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/ManyToManyResolver.java:166— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/ManyToManyResolver.java:166-179 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyResolver.java:186-199 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (14 lines × 2) spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/bean/BeanRepositoryQuery.java:86— spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/bean/BeanRepositoryQuery.java:86-99 | spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/bean/QueryRepositoryQuery.java:90-103 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (12 lines × 2) sql-adapter/sql-mariadb-adapter/src/main/java/org/codefilarete/stalactite/sql/mariadb/statement/binder/MariaDBTypeMapping.java:20— sql-adapter/sql-mariadb-adapter/src/main/java/org/codefilarete/stalactite/sql/mariadb/statement/binder/MariaDBTypeMapping.java:20-31 | sql-adapter/sql-mysql-adapter/src/main/java/org/codefilarete/stalactite/sql/mysql/statement/binder/MySQLTypeMapping.java:20-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (12 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithMappedAssociationEngine.java:96— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithMappedAssociationEngine.java:96-107 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyWithMappedAssociationEngine.java:83-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (12 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToManyMetadataResolver.java:292— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToManyMetadataResolver.java:292-304 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyRelationConfigurer.java:235-246 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (12 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/embeddable/FluentEmbeddableMappingConfigurationSupport.java:491— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/embeddable/FluentEmbeddableMappingConfigurationSupport.java:491-502 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/EntityDecoratedEmbeddableConfigurationSupport.java:136-147 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (12 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyMapRelationConfigurer.java:157— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyMapRelationConfigurer.java:157-168 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsValueMapRelationConfigurer.java:156-167 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (12 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/AggregateManyToManyAppender.java:337— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/AggregateManyToManyAppender.java:337-349 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/AggregateOneToManyWithIndexedAssociationTableAppender.java:192-203 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (12 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/AggregateMapAppender.java:83— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/AggregateMapAppender.java:83-95 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/AggregateMapAppender.java:114-125 — 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 (12 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/AggregateOneToManyWithIndexedAssociationTableAppender.java:164— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/AggregateOneToManyWithIndexedAssociationTableAppender.java:164-175 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/AggregateOneToManyWithIndexedMappedAssociationAppender.java:122-133 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (5 lines × 2) core/src/main/java/org/codefilarete/stalactite/sql/statement/DMLGenerator.java:177— core/src/main/java/org/codefilarete/stalactite/sql/statement/DMLGenerator.java:177-181 | core/src/main/java/org/codefilarete/stalactite/sql/statement/DMLGenerator.java:228-232 — 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) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/jointable/JoinTablePolymorphismPersister.java:108— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/jointable/JoinTablePolymorphismPersister.java:108-112 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/singletable/SingleTablePolymorphismPersister.java:119-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (5 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/AbstractPolymorphicEntityFinder.java:176— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/AbstractPolymorphicEntityFinder.java:176-180 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/RelationalEntityFinder.java:278-282 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (5 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/cascade/AfterUpdateSupport.java:36— orm/src/main/java/org/codefilarete/stalactite/engine/cascade/AfterUpdateSupport.java:36-40 | orm/src/main/java/org/codefilarete/stalactite/engine/cascade/BeforeUpdateSupport.java:36-40 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (5 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyCycleConfigurer.java:44— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyCycleConfigurer.java:44-48 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetomany/OneToManyCycleConfigurer.java:42-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (5 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/SkeletonAggregateResolver.java:106— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/SkeletonAggregateResolver.java:106-110 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/SkeletonAggregateResolver.java:118-126 — 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 (19 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:100— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:100-118 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetoone/OneToOneOwnedByTargetEngine.java:101-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (19 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:210— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedByTargetEngine.java:210-228 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetoone/OneToOneOwnedByTargetEngine.java:211-229 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (19 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/EntityDecoratedEmbeddableConfigurationSupport.java:83— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/EntityDecoratedEmbeddableConfigurationSupport.java:83-101 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/FluentSubEntityMappingConfigurationSupport.java:581-599 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 3) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/jointable/JoinTablePolymorphismEntityFinder.java:159— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/jointable/JoinTablePolymorphismEntityFinder.java:159-166 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/singletable/SingleTablePolymorphismEntityFinder.java:164-175 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/tableperclass/TablePerClassPolymorphismEntityFinder.java:260-271 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 3) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/jointable/JoinTablePolymorphismPersister.java:125— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/jointable/JoinTablePolymorphismPersister.java:125-132 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/singletable/SingleTablePolymorphismPersister.java:136-143 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/tableperclass/TablePerClassPolymorphismPersister.java:126-133 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (8 lines × 3) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/jointable/JoinTablePolymorphismPersister.java:166— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/jointable/JoinTablePolymorphismPersister.java:166-173 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/singletable/SingleTablePolymorphismPersister.java:173-180 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/tableperclass/TablePerClassPolymorphismPersister.java:160-167 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (21 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/MapRelationConfigurer.java:241— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/MapRelationConfigurer.java:241-262 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/EntryMapResolver.java:163-183 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (21 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/AggregateManyToManyAppender.java:265— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytomany/AggregateManyToManyAppender.java:265-285 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/AggregateOneToManyWithIndexedAssociationTableAppender.java:119-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (20 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedAssociationTableEngine.java:249— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedAssociationTableEngine.java:249-268 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyWithIndexedAssociationTableEngine.java:142-161 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (20 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytoone/AggregateManyToOneAppender.java:87— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytoone/AggregateManyToOneAppender.java:87-106 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetoone/AggregateOneToOneAppender.java:111-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (18 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithAssociationTableEngine.java:180— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithAssociationTableEngine.java:180-197 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyWithAssociationTableEngine.java:121-138 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (18 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/FluentEntityMappingConfigurationSupport.java:876— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/FluentEntityMappingConfigurationSupport.java:876-893 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/FluentSubEntityMappingConfigurationSupport.java:405-422 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (12 lines × 3) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/ElementCollectionRelation.java:244— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/ElementCollectionRelation.java:244-255 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyRelation.java:202-213 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetomany/OneToManyRelation.java:293-304 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (12 lines × 3) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyAndValueMapRelationConfigurer.java:141— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyAndValueMapRelationConfigurer.java:141-152 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsKeyMapRelationConfigurer.java:140-151 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/EntityAsValueMapRelationConfigurer.java:139-150 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (5 lines × 3) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/load/EntityJoinTree.java:314— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/load/EntityJoinTree.java:314-318 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/load/EntityJoinTree.java:328-332 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/load/EntityJoinTree.java:347-351 — 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 × 3) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/ElementRecordMapping.java:172— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/ElementRecordMapping.java:172-176 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/ElementRecordMapping.java:222-226 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/IndexedElementRecordMapping.java:228-232 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
AbstractDerivedQuery.convertToCriterion (cyclomatic 41) spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/derivation/AbstractDerivedQuery.java:43— AbstractDerivedQuery.convertToCriterion has cyclomatic complexity 41 (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.
OneToManyOwnedByTargetHelper.determineForeignKeyColumns (cyclomatic 16) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java:207— OneToManyOwnedByTargetHelper.determineForeignKeyColumns 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.
OneToManyWithMappedAssociationConfigurer.determineForeignKeyColumns (cyclomatic 16) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetomany/OneToManyWithMappedAssociationConfigurer.java:84— OneToManyWithMappedAssociationConfigurer.determineForeignKeyColumns 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.
EmbeddedClassMapping.getUpdateValues (cyclomatic 16) core/src/main/java/org/codefilarete/stalactite/mapping/EmbeddedClassMapping.java:251— EmbeddedClassMapping.getUpdateValues 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.
Hotspot: orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java changed 4 times in last 90 days, max complexity 16.
ManyToManyMetadataResolver.buildReverseCombiner (cognitive 31) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToManyMetadataResolver.java:246— ManyToManyMetadataResolver.buildReverseCombiner has cognitive complexity 31 (threshold 15). Drivers by points: if/else 30, 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.
OneToManyMetadataResolver.resolve (cognitive 31) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java:86— OneToManyMetadataResolver.resolve has cognitive complexity 31 (threshold 15). Drivers by points: if/else 23, ternaries 8 (nesting depth added 18). 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.
ManyToManyWithAssociationTableConfigurer.buildReverseCombiner (cognitive 28) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytomany/ManyToManyRelationConfigurer.java:192— ManyToManyWithAssociationTableConfigurer.buildReverseCombiner has cognitive complexity 28 (threshold 15). Drivers by points: if/else 27, 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.
1.apply (cognitive 26) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/load/EntityTreeInflater.java:116— 1.apply has cognitive complexity 26 (threshold 15). Drivers by points: if/else 22, ternaries 4 (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.
ColumnedMapMapping.getUpdateValues (cognitive 26) core/src/main/java/org/codefilarete/stalactite/mapping/ColumnedMapMapping.java:88— ColumnedMapMapping.getUpdateValues has cognitive complexity 26 (threshold 15). Drivers by points: loops 10, if/else 8, ternaries 6, boolean chains 2 (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.
ManyToOneMetadataResolver.buildReverseCombiner (cognitive 25) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToOneMetadataResolver.java:229— ManyToOneMetadataResolver.buildReverseCombiner has cognitive complexity 25 (threshold 15). Drivers by points: if/else 24, boolean chains 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.
OneToManyOwnedByTargetHelper.determineForeignKeyColumns (cognitive 25) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java:207— OneToManyOwnedByTargetHelper.determineForeignKeyColumns has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17, ternaries 6, boolean chains 2 (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.
ManyToOneConfigurer.buildReverseCombiner (cognitive 25) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/manytoone/ManyToOneConfigurer.java:138— ManyToOneConfigurer.buildReverseCombiner has cognitive complexity 25 (threshold 15). Drivers by points: if/else 24, boolean chains 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.
OneToManyWithMappedAssociationConfigurer.determineForeignKeyColumns (cognitive 25) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/onetomany/OneToManyWithMappedAssociationConfigurer.java:84— OneToManyWithMappedAssociationConfigurer.determineForeignKeyColumns has cognitive complexity 25 (threshold 15). Drivers by points: if/else 17, ternaries 6, boolean chains 2 (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.
IdentifierManagerStep.determineIdentifierManager (cognitive 21) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/IdentifierManagerStep.java:62— IdentifierManagerStep.determineIdentifierManager has cognitive complexity 21 (threshold 15). Drivers by points: if/else 21 (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.
AbstractDerivedQuery.convertToCriterion (cognitive 21) spring-integration/spring-data/src/main/java/org/codefilarete/stalactite/spring/repository/query/derivation/AbstractDerivedQuery.java:43— AbstractDerivedQuery.convertToCriterion has cognitive complexity 21 (threshold 15). Drivers by points: if/else 18, boolean chains 2, match/switch 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.
AggregateResolver.collectTables (cognitive 19) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/AggregateResolver.java:400— AggregateResolver.collectTables has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18, loops 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.
EmbeddedClassMapping.getUpdateValues (cognitive 19) core/src/main/java/org/codefilarete/stalactite/mapping/EmbeddedClassMapping.java:251— EmbeddedClassMapping.getUpdateValues has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11, boolean chains 5, loops 2, ternaries 1 (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.
DefaultEntityMapping.getUpdateValues (cognitive 18) core/src/main/java/org/codefilarete/stalactite/mapping/DefaultEntityMapping.java:292— DefaultEntityMapping.getUpdateValues has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7, loops 7, ternaries 3, boolean chains 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.
CollectionUpdater.set (cognitive 16) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/CollectionUpdater.java:99— CollectionUpdater.set has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5, if/else 4, loops 4, boolean chains 3 (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.
EntryMapResolver.resolve (cognitive 16) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/map/EntryMapResolver.java:80— EntryMapResolver.resolve has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, ternaries 4, boolean chains 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.
ColumnedCollectionMapping.getUpdateValues (cognitive 16) core/src/main/java/org/codefilarete/stalactite/mapping/ColumnedCollectionMapping.java:94— ColumnedCollectionMapping.getUpdateValues has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6, loops 6, boolean chains 2, ternaries 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.
ZonedDateTimeMapping.getUpdateValues (cognitive 16) core/src/main/java/org/codefilarete/stalactite/mapping/ZonedDateTimeMapping.java:95— ZonedDateTimeMapping.getUpdateValues has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, ternaries 4, loops 2, boolean chains 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.
Medium: use-of-md5 orm/src/main/java/org/codefilarete/stalactite/dsl/naming/ForeignKeyNamingStrategy.java:108— Detected MD5 hash algorithm which is considered insecure. MD5 is not collision resistant and is therefore not suitable as a cryptographic signature. Use HMAC instead. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
Duplicated block (24 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:172— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:172-195 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:64-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (22 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithMappedAssociationEngine.java:180— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithMappedAssociationEngine.java:180-201 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetomany/OneToManyWithMappedAssociationEngine.java:133-154 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (18 lines × 3) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/embeddable/FluentEmbeddableMappingConfigurationSupport.java:694— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/embeddable/FluentEmbeddableMappingConfigurationSupport.java:694-711 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/FluentEntityMappingConfigurationSupport.java:687-704 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/FluentSubEntityMappingConfigurationSupport.java:246-263 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (17 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/FluentCompositeKeyMappingConfigurationSupport.java:168— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/FluentCompositeKeyMappingConfigurationSupport.java:168-184 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/FluentCompositeKeyMappingConfigurationSupport.java:220-236 — 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 (16 lines × 3) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/embeddable/FluentEmbeddableMappingConfigurationSupport.java:738— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/embeddable/FluentEmbeddableMappingConfigurationSupport.java:738-753 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/FluentEntityMappingConfigurationSupport.java:731-746 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/FluentSubEntityMappingConfigurationSupport.java:290-305 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (15 lines × 3) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/embeddable/FluentEmbeddableMappingConfigurationSupport.java:774— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/embeddable/FluentEmbeddableMappingConfigurationSupport.java:774-788 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/FluentEntityMappingConfigurationSupport.java:767-782 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/FluentSubEntityMappingConfigurationSupport.java:326-340 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (15 lines × 2) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/embeddable/FluentEmbeddableMappingConfigurationSupport.java:299— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/embeddable/FluentEmbeddableMappingConfigurationSupport.java:299-313 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/FluentEntityMappingConfigurationSupport.java:1087-1101 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (13 lines × 4) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithAssociationTableEngine.java:93— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithAssociationTableEngine.java:93-105 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedAssociationTableEngine.java:79-91 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithIndexedMappedAssociationEngine.java:81-93 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetomany/OneToManyWithMappedAssociationEngine.java:142-154 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (12 lines × 4) orm/src/main/java/org/codefilarete/stalactite/engine/runtime/manytoone/ManyToOneEngine.java:103— orm/src/main/java/org/codefilarete/stalactite/engine/runtime/manytoone/ManyToOneEngine.java:103-114 | orm/src/main/java/org/codefilarete/stalactite/engine/runtime/onetoone/OneToOneOwnedBySourceEngine.java:93-104 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/manytoone/ManyToOneEngine.java:104-115 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/onetoone/OneToOneOwnedBySourceEngine.java:94-105 — the copies span different directories, so extracting a shared function means choosing where it lives: put it wherever the callers may both depend on (the module they already share, or a small common one if they share none) and call it from each site — until then, every change has to be made twice.
Duplicated block (10 lines × 3) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/ElementRecordMapping.java:149— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/ElementRecordMapping.java:149-158 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/ElementRecordMapping.java:206-215 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/elementcollection/IndexedElementRecordMapping.java:209-218 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (6 lines × 4) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToManyMetadataResolver.java:224— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToManyMetadataResolver.java:224-230 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/ManyToOneMetadataResolver.java:146-152 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToManyMetadataResolver.java:187-192 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/dslresolver/OneToOneMetadataResolver.java:126-131 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (5 lines × 4) orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/MapEntryKeyAndValueEntitiesUpdater.java:180— orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/MapEntryKeyAndValueEntitiesUpdater.java:180-184 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/MapEntryKeyAndValueEntitiesUpdater.java:188-192 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/MapEntryKeyAndValueEntitiesUpdater.java:196-200 | orm/src/main/java/org/codefilarete/stalactite/engine/configurer/map/MapEntryKeyAndValueEntitiesUpdater.java:204-208 — 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.
Recommendation — 5 finding(s)
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — Test source is present (.java) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 232 significant file(s) lose their only recent owner: orm/src/main/java/org/codefilarete/stalactite/engine/configurer/entity/FluentEntityMappingConfigurationSupport.java, orm/src/main/java/org/codefilarete/stalactite/dsl/entity/FluentEntityMappingBuilder.java, orm/src/main/java/org/codefilarete/stalactite/engine/runtime/load/EntityJoinTree.java, orm/src/main/java/org/codefilarete/stalactite/engine/configurer/embeddable/FluentEmbeddableMappingConfigurationSupport.java, core/src/main/java/org/codefilarete/stalactite/engine/QueryMapper.java, orm/src/main/java/org/codefilarete/stalactite/engine/runtime/tableperclass/TablePerClassPolymorphismPersister.java, orm/src/main/java/org/codefilarete/stalactite/engine/configurer/resolver/AggregateResolver.java, orm/src/main/java/org/codefilarete/stalactite/engine/configurer/builder/embeddable/EmbeddableMappingBuilder.java (+224 more). Pair on, review, or document these before any departure.
D19 · Documentation Quality· The adaptation layer for PostgreSQL is described only in a truncated section ('Specifies adhoc PostgreSQL SQL types...') and no further details on how it maps JDBC types to the database schema. · ×1
The adaptation layer for PostgreSQL is described only in a truncated section ('Specifies adhoc PostgreSQL SQL types...') and no further details on how it maps JDBC types to the database schema. sql-adapter/sql-postgresql-adapter/README.md— Expand this README to describe the supported PostgreSQL SQL type mappings, any dialect-specific configuration, and an example of how a JDBC column is translated into a query parameter.
D38 · OSV Dependency Vulnerabilities· Scanner failed to run · ×1
Scanner failed to run — not a clean result — osv-scanner exited 128 with no findings — the advisory database was likely unreachable. The scanner exited non-zero and produced no findings (typically the advisory DB was unreachable), so this is reported as a measurement gap rather than a clean pass.
Coverage not included — suite not readable by the collector — Coverage NOT MEASURED: test source is present (.java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored.
Info — 2 finding(s)
D12 · Dependency Hygiene· Dependency hygiene not measured · ×1
Dependency hygiene not measured — dependency manifest found but not parsed for hygiene — This repository's dependency manifest (a Maven POM) was found, but this pass cannot parse it for hygiene, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D38 wherever the manifest is OSV-readable.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
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, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines.yml, Jenkinsfile, .circleci); there is no build to attest provenance for.
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.
0
—
Run 019fb006-11ee-74eb-b23d-cf8b4482daec · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Warnings: 214 · Recommendations: 5 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 29-07-2026 @ 22:36 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.