hboutemy opened a new pull request, #12555: URL: https://github.com/apache/maven/pull/12555
improve documentation of the deprecation in `plugin.xml`'s `<requirement>`, as recently we discovered that injection with `MavenPluginManager.getConfiguredMojo(...)` does not provide same result than direct JSR 330 = https://github.com/eclipse-tycho/tycho/pull/6195#issuecomment-5089230625 (notice: I still don't fully understand, but now it seems it's not only a question of "modern" style preference) in parallel to Maven core documentation improvement, we should probably also: 1. help plugin writers: update Plugin Tools to warn when it generates a `plugin.xml` that contains such `<requirements>` (in general from [`@Component`](https://github.com/apache/maven-plugin-tools/blob/maven-plugin-tools-3.15.2/maven-plugin-annotations/src/main/java/org/apache/maven/plugins/annotations/Component.java) annotations) 2. help plugin consumers: once we help plugin writers, I suppose we can also warn plugin users with a new [plugin validation](https://maven.apache.org/guides/plugins/validation/index.html) -- 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]
