laomo-hub opened a new pull request, #7688:
URL: https://github.com/apache/shenyu/pull/7688

   Refs #7679.
   
   `shenyu-common` resolves conflicting versions of annotation artifacts 
through Caffeine, Guava and Gson. Caffeine also causes `checker-qual` to 
resolve below Guava's requested version.
   
   Manage `checker-qual` at 3.33.0 and `error_prone_annotations` at 2.41.0 in 
the root POM, matching the highest versions already requested on the reproduced 
paths.
   
   This is an incremental slice of #7679. Framework BOMs, SLF4J and Enforcer 
activation remain outside this change. Scope coordination: 
https://github.com/apache/shenyu/issues/7679#issuecomment-6220604377
   
   Validation (JDK 17, repository Maven wrapper):
   - Reproduced annotation convergence and checker upper-bound failures before 
the change.
   - DependencyConvergence passes for `shenyu-common` and its selected 
four-project reactor afterward. Combined Enforcer still exits 1 for the 
existing SLF4J upper-bound conflict; the annotation failures are gone.
   - `./mvnw -B -ntp -pl shenyu-common -am verify -Dmaven.javadoc.skip=true 
-DskipRemoteResources=true`: BUILD SUCCESS; 507 reported tests, 0 
failures/errors, 1 existing skip (506 passed). Checkstyle and Apache RAT pass.
   - `git diff --check` passes.
   - Full-repository clean install not run.
   
   Make sure that:
   - [x] You have read the [contribution 
guidelines](https://shenyu.apache.org/community/contributor-guide).
   - [ ] You submit test cases (unit or integration tests) that back your 
changes. This POM-only change was validated with existing tests and 
before/after Enforcer checks.
   - [ ] Your local test passed `./mvnw clean install 
-Dmaven.javadoc.skip=true`. Only the scoped reactor verification above was run.
   
   Draft pending maintainer confirmation of the scoped contribution.


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