[igel-devin-ai]

Summary

Closes #378 — generalizes BuilderProcessor's machinery into a reusable annotation-processing framework before the module move (#349). A new org.javahelpers.codegen.processing package holds the generic pipeline; BuilderProcessor shrinks to the builder domain plugged into it via hooks. Generated output is byte-identical.

The generic machinery (new package codegen.processing)

• AbstractCodegenProcessor<C, K, D> — the driver. Owns the processing lifecycle so a new processor supplies only its domain hooks:

  ctx      = createContext(env, reader, logger)                   [implement]
  per round:
    onRoundStart(ctx)                                           [no-op hook]
    elements = findElements(annotations, roundEnv)              [default: config's elementCollector]
    skipsRound(elements, ctx)  → empty collection or isFinished(ctx)  [framework gate]
    tasks    = plan(elements, ctx)  → planTasks(elements, ctx)  [implement]
    onTasksPlanned(tasks, ctx)                                  [no-op hook]
    registerPlannedTaskResults(tasks, ctx)                      [framework; per-task names via predictTaskResultTypeNames() — default: empty]
    loop 1 — specification (guarded, strict-mode reporting):
      defs   = analyse(task, ctx)                               [implement]
      target = mapToTargetSpecification(def, cfg, ctx)          [implement — one def, one target]
    loop 2 — generation:
      existsGuard → generateTarget(target)                      [engine + formatterResolver.resolve(target.mode)]
      onTaskGenerated(PlannedGeneration, ctx)                   [no-op hook]
    endRound(ctx)                                               [no-op hook — also after an empty plan]
  last round: onProcessingOver(ctx)                             [no-op hook — domain generates last-round outputs via generateTarget]
  

• CodegenProcessorConfiguration — static declarations in one record handed to super(...): elementCollector (required), optionRegistry, requiredSourceVersion, loggerPrefix (default: processor class name).

• ElementCollector/ElementSelector/ElementGroups — declarative element selection keyed by group name (annotation types, meta-marker metaMarked, opt-out); collection only finds, value reading stays in planTasks.

• ProcessorOptionRegistry — supported options derived as a Set from the declared CompilerOptions, including the wired verbose and formatter-profile options.

• CodegenTask<K> — the planned unit (element + resolved configuration + output package); PlannedGeneration (protected record) carries task + definition + target into onTaskGenerated.

• CodegenConfiguration/CodegenDefinition — the domain contracts (targetTypeName() = the generated type's predicted name).

• SourceFormatterResolver — formatter profile resolved from the option registry.

• GenerationEnvironment wiring (generationEnvironment(...)), target-exists guard, JDK gate (verifySupportedJdk), and the generated-type registry all live in the driver.

BuilderProcessor after the collapse

Only domain code remains: ELEMENT_COLLECTOR/OPTION_REGISTRY/PROCESSOR_CONFIGURATION constants, createContext, createGenerator (RoasterCodeGenerator over generationEnvironment(...)), planTasks (config resolution, @SimpleBuilderFor expansion, scope/conflict rules), predictTaskResultTypeNames + onTaskResultRegistered (builder-name registration + SPI publication), analyse/mapToTargetSpecification, onTaskGenerated (Jackson accumulation + metrics), onProcessingOver (SPI flush, Jackson modules via generateTarget, perf report), isFinished/endRound (once-round marker + SPI finalization). ~600 lines of driver code left the class.

Verification

• mvn clean install — 567/567 tests green (processor 535); pinned diagnostic strings unchanged (domain keeps its "builder"/"Jackson module" nouns, framework messages use "target")
• mvn -pl example clean compile after removing generated-example-builder — regenerated sources byte-identical (git status clean)
• CodeQL: genuinely-dead java/unused-parameter params removed; the remaining ones are intentional extension-point parameters, dismissed as "won't fix" in the Security tab (CodeQL suppression comments are not honored by code scanning without an extra dismiss Action)
• SonarCloud quality gate: passed

This lands before the #368 module move: the move PR then carries a third artifact (annotation-processing) holding this package plus the JSR-269-bound helpers, per the plan discussion.

Lifecycle parity with main: a round with collected elements but an empty plan (e.g. every @SimpleBuilder outside builderGenerationPackages) still runs endRound → finishCompilation(), so MapStruct maps such beans via setters instead of deferring until "No implementation was created" — pinned by MapStructSpiIntegrationTest.mapStruct_markedBeanOutsideGenerationScope_shouldMapViaSetters.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
93.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud