[
https://issues.apache.org/jira/browse/MNG-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636558#comment-17636558
]
ASF GitHub Bot commented on MNG-7598:
-------------------------------------
gnodet commented on PR #874:
URL: https://github.com/apache/maven/pull/874#issuecomment-1321706362
I think it needs to be enabled on not only maven-core. It's missing stuff
like
https://github.com/apache/maven/pull/841/files#diff-a660bdaa2e580478c65a557fd7001c80e129c0e9d4766840b4072c3b72c1863f
> Enforce binary backwards-compatibility with Maven 3 of all exported packages
> ----------------------------------------------------------------------------
>
> Key: MNG-7598
> URL: https://issues.apache.org/jira/browse/MNG-7598
> Project: Maven
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: 4.0.0
>
>
> All packages exported through the API classloader (indicated in
> https://github.com/apache/maven/blob/master/maven-core/src/main/resources/META-INF/maven/extension.xml)
> should be binary backwards-compatible in Maven 4.
> To enforce this the
> [japicmp-maven-plugin|https://siom79.github.io/japicmp/MavenPlugin.html]
> should be leveraged during the build.
> Compare with the discussion at
> https://lists.apache.org/thread/l8brfb69z2vclds1v91j7x98fp9ls7rj.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
