[
https://issues.apache.org/jira/browse/MNG-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17913875#comment-17913875
]
Guillaume Nodet commented on MNG-8525:
--------------------------------------
There may be a release cycle problem in doing so.
One of the reason is that a Maven 4 plugin will require {{maven-plugin-tools}}
and {{maven-plugin-testing}} with recent versions. In case of an incompatible
breakage, it may happen that those tools need to be update with the current
release of Maven.
Anyway, we'll see. Worst thing, we don't _build_ the plugin, but just _use_ it.
Here's a simple example of such a Maven 4 plugin:
[https://github.com/apache/maven-clean-plugin/blob/master/src/main/java/org/apache/maven/plugins/clean/CleanMojo.java]
> Add an integration test with Maven 4 Plugin Sample
> --------------------------------------------------
>
> Key: MNG-8525
> URL: https://issues.apache.org/jira/browse/MNG-8525
> Project: Maven
> Issue Type: Improvement
> Components: Documentation: Guides, Integration Tests
> Reporter: Sandra Parsick
> Priority: Trivial
>
> To show how to use Maven DI in plugins, a sample code is helpful. To ensure
> that the sample code is valid, it should be implemented as an integration
> test.
> see also the integration test MNG-5382 for
> [JSR330Plugins|https://github.com/apache/maven-integration-testing/tree/master/core-it-suite/src/test/resources/mng-5382]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
