[
https://issues.apache.org/jira/browse/MNG-8098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MNG-8098:
---------------------------------
Description:
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...
was: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.
> 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)
