You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/11/16 10:58:00 UTC
[jira] [Commented] (MNG-7598) Enforce binary backwards-compatibility with Maven 3 of all exported packages
[ https://issues.apache.org/jira/browse/MNG-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634778#comment-17634778 ]
ASF GitHub Bot commented on MNG-7598:
-------------------------------------
kwin opened a new pull request, #874:
URL: https://github.com/apache/maven/pull/874
For now only enabled in core and plugin-api
Currently breaks build due to incompatible changes compared to 3.8.6
> 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://siom79.github.io/japicmp/MavenPlugin.html.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)