[
https://issues.apache.org/jira/browse/MNG-8494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910553#comment-17910553
]
Guillaume Nodet commented on MNG-8494:
--------------------------------------
[~slachiewicz] you mean for plugins ?
The rules are quite simple
* the plugin can only depend on `org.apache.maven:maven-api-*` artifacts (no
any other maven related artifacts) at compile time
* avoid plexus artifacts at compile time
* mojo annotations are now in {{org.apache.maven.api.plugin.annotations}}
package
* injection annotations come from {{org.apache.maven.api.di}}
* replace {{MavenSession}} with {{org.apache.maven.api.Session}},
{{MavenProject}} with {{org.apache.maven.api.Project}},
{{org.apache.maven.model.*}} with {{org.apache.maven.api.model.*}}
* unit test needs JUnit 5 and need the {{org.apache.maven.api.plugin.testing}}
> Restore Maven 3 compatibility
> -----------------------------
>
> Key: MNG-8494
> URL: https://issues.apache.org/jira/browse/MNG-8494
> Project: Maven
> Issue Type: Task
> Components: API
> Reporter: Guillaume Nodet
> Priority: Critical
> Fix For: 4.0.0-rc-3
>
>
> The Maven 3 modules have been moved into the {{/compat/}} directory.
> But before this happened and the new Maven 4 API was introduced, those
> classes undergo quite some incompatible changes. Given they are now
> deprecated, it would make sense to restore them to full Maven 3.9.x
> compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
