stevearmstrong-dev opened a new pull request, #11480:
URL: https://github.com/apache/maven/pull/11480

   ## Summary
   - Remove `slf4j-simple` test dependency from `maven-core` (which already has 
`maven-logging`)
   - Replace `slf4j-simple` with `maven-logging` in `maven-impl` and 
`maven-resolver-provider` test dependencies
   - Eliminates "multiple SLF4J providers" warnings when running tests
   
   ## Background
   Maven has its own SLF4J provider 
(`org.apache.maven.slf4j.MavenServiceProvider`) in the `maven-logging` module. 
Having `slf4j-simple` as a test dependency creates a conflict that produces 
warnings like:
   
   ```
   SLF4J(W): Class path contains multiple SLF4J providers.
   SLF4J(W): Found provider 
[org.apache.maven.slf4j.MavenServiceProvider@5c45d770]
   SLF4J(W): Found provider [org.slf4j.simple.SimpleServiceProvider@2ce6c6ec]
   ```
   
   ## Changes
   - **maven-core**: Removed `slf4j-simple` test dependency (already depends on 
`maven-logging`)
   - **maven-impl**: Replaced `slf4j-simple` with `maven-logging` test 
dependency
   - **maven-resolver-provider**: Replaced `slf4j-simple` with `maven-logging` 
test dependency
   
   This ensures all modules use Maven's own SLF4J provider consistently.
   
   ## Test plan
   - [ ] Full test suite passes (`mvn -Prun-its verify`)
   - [ ] No SLF4J multiple provider warnings in test output
   - [ ] CI build succeeds
   
   Fixes #10949


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