gnodet commented on issue #12571:
URL: https://github.com/apache/maven/issues/12571#issuecomment-6212300809

   ## PR Stack and Sub-issues
   
   Tracking the implementation PRs and follow-up issues for the build output 
overhaul.
   
   ### PR stack (in merge order)
   
   | # | PR | Feature | Status |
   |---|---|---|---|
   | 0 | #13542 | BuildEnvironment API (prerequisite) | Open |
   | 1 | #12694 | Logging foundation: LogEvent, JUL handler, LogSink | Open |
   | 2 | #12695 | Build report: structured JSON with per-mojo log capture | 
Open |
   | 3 | #13180 | Console modes: `--console=plain/rich/verbose/machine` | Open |
   | 4 | #12698 | Warning mode, DiagnosticCollector, BuilderProblem enrichments 
| Open |
   | 5 | #12699 | `mvnlog` viewer, integration tests, script routing | Open |
   | 6 | #12702 | Structured BuilderProblem pipeline (rebasing onto master) | 
Open |
   | 7 | #12714 | TRACE level migration (rebasing onto master independently) | 
Open |
   
   ### Follow-up issues
   
   - [ ] #12643 — Remaining BuilderProblem piping (settings/toolchains 
validation)
   - [ ] #12644 — Compiler plugin structured diagnostics
   - [ ] #12645 — `mvnlog --web` viewer
   - [ ] #11088 — CI env variable defaults
   - [ ] #13562 — Unified v4 event bus: DiagnosticEvent, TransferEvent, LogEvent
   - [ ] #13563 — `--warning-mode=summary` must actually suppress inline 
warnings
   - [ ] #13564 — Build report schema versioning (`reportVersion` field)
   - [ ] #13565 — SLF4J 2.0 key-value conventions for plugin diagnostic metadata
   - [ ] #13566 — Partial build report via shutdown hook on crash
   - [ ] #13567 — OTel correlation IDs in build report
   
   ### Known bugs to fix in PRs
   
   - [ ] `DefaultDiagnosticCollector`: `LongAdder` race condition in synthetic 
key generation → replace with `AtomicLong.incrementAndGet()` (#12698)
   - [ ] `BuildReportCollector`: `hasWarnings()` / `warningCount` mismatch — 
`hasWarnings()` includes ERROR severity but count only counts WARNING (#12698)
   - [ ] `SimpleJsonReader`: no recursion depth limit — add `MAX_DEPTH = 512` 
guard (#12699)
   
   ### Design notes from review
   
   - **Chain restructuring**: #12714 (TRACE migration) and #12702 (structured 
problems) are being rebased onto master independently to reduce the critical 
merge path from 8 to 6 PRs.
   - **Event bus unification**: The logging PRs add `DiagnosticReporter` as a 
service and `LogSink` as a callback, bypassing the v4 `Event`/`Listener` 
hierarchy. #13562 tracks extending the v4 event bus to unify all these systems.
   - **Warning mode gap**: `--warning-mode=summary` and `--warning-mode=all` 
are currently functionally identical. #13563 tracks the suppression mechanism 
needed to make them different.
   
   _Claude Code on behalf of Guillaume Nodet_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to