slachiewicz opened a new issue, #14072:
URL: https://github.com/apache/maven/issues/14072

   Tracking issue for a read-first simplification sweep of the 
shared-component, utility, and Doxia repositories listed in #13085.
   
   Phase 1 scanned 25 active repositories and produced a proposal report. The 
repositories were scanned at the current remote default branch with no local 
edits. The proposals are limited to small, behavior-preserving changes in four 
areas: production code, tests, documentation, and build/setup configuration. 
Each change is delivered as one labelled draft pull request per repository and 
concern.
   
   `maven-shared-incremental` is excluded because the repository is archived. 
`maven-mapping` and `maven-dependency-tree` produce no pull requests because 
they are retirement candidates with in-flight changes covering the candidate 
areas.
   
   Categories of work:
   
   - Production: remove dead and commented-out code, drop redundant 
initializers, replace manual loops with Java 8-compatible streams, and simplify 
empty-collection checks.
   - Tests: convert copy-pasted cases to JUnit 5 parameterized tests, use 
`assertThrows` and `assertAll`, and remove vacuous or dead test code.
   - Documentation: replace dead links and stale Jenkins badges with current 
URLs, remove unused link definitions and unused instructions, and fix Javadoc 
typos.
   - Build/setup: remove empty `<profiles>` elements, unused POM properties, 
dead plugin configuration, and no-op workflow inputs.
   
   Changes whose semantics are not behavior-identical, that need a new 
dependency not managed by the parent BOM, or that touch areas covered by an 
open pull request are left out.
   
   Verification for each pull request:
   
   1. Build and test against the current remote default branch with the JDK 
used by the repository's CI.
   2. For test changes, compare per-class surefire counts before and after and 
mutation-check one new assertion.
   3. For documentation changes, recheck every touched URL and render affected 
site pages.
   4. For workflow changes, validate JSON and YAML locally.
   5. Keep test counts, commit only tracked files, and use one concern per pull 
request.
   
   Pull requests are linked to this issue. Progress and results are reported 
here as the sweep proceeds.
   


-- 
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