[
https://issues.apache.org/jira/browse/MNG-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17837373#comment-17837373
]
Slawomir Jaranowski commented on MNG-8098:
------------------------------------------
I would like to consider a new branch for such cases - we can crate a branch
3.x and go in master only with Maven 4.
We will have the same situation for all other plugins - we will want to release
version for Maven 4 but also want to maintain for Maven 3
> Move m-plugin-plugin and m-plugin-testing into maven-core
> ---------------------------------------------------------
>
> Key: MNG-8098
> URL: https://issues.apache.org/jira/browse/MNG-8098
> Project: Maven
> Issue Type: New Feature
> Reporter: Guillaume Nodet
> Priority: Major
> Fix For: 4.0.x-candidate
>
>
> With the Maven 4 API still being in flux, I think we should move the
> maven-plugin-plugin support for 4.x plugins along with the test
> infrastructure for those plugins in maven core, so that they would have the
> same lifecycle than the API.
> Especially now than Maven 4 targets JDK 17, supporting both Maven 3 and 4 in
> the same plugin is a bit more difficult... and that would definitely clean
> those two projects...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)