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

   A scan of the local Apache Maven estate on 2026-11-20 found nine 
plugin/project 4.x lines still importing `org.apache.maven.api.plugin.Log` and 
pinning a 4.0.0 release candidate. The new 
`org.apache.maven.api.logging.Logger` API in #14066 replaces that interface.
   
   Plan: for each repository, replace `Log` with `Logger`, set the Maven 
dependency version to `4.0.0-SNAPSHOT`, verify compilation against a locally 
built Maven 4.0.0-SNAPSHOT, and open a labelled draft pull request. The draft 
PRs stay open until the new API is published.
   
   Repositories in scope:
   - maven-clean-plugin (`maven-clean-plugin-4.x`)
   - maven-compiler-plugin (`maven-compiler-plugin-4.x`)
   - maven-deploy-plugin (`maven-deploy-plugin-4.x`)
   - maven-install-plugin (`maven-install-plugin-4.x`)
   - maven-jar-plugin (`maven-jar-plugin-4.x`)
   - maven-plugin-tools (`master`)
   - maven-resources-plugin (`maven-resources-plugin-4.x`)
   - maven-site (`master`)
   - maven-source-plugin (`maven-source-plugin-4.x`)
   
   Known gap: `maven-testing`'s `MojoExtension` only binds `Log`. Tests that 
inject a Mojo through the extension will fail until it also binds `Logger`.
   


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