You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2022/09/01 08:56:00 UTC

[jira] [Commented] (FLINK-25868) Enable japicmp for all modules

    [ https://issues.apache.org/jira/browse/FLINK-25868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598825#comment-17598825 ] 

Chesnay Schepler commented on FLINK-25868:
------------------------------------------

The issues have been resolved in the latest 1.16.0 version, but said version is no longer compatible with Maven 3.2.5. I published a [custom version|https://search.maven.org/artifact/io.github.zentol.japicmp/japicmp-maven-plugin/0.16.0_m325/maven-plugin] that we can leverage until FLINK-28016 is complete.

> Enable japicmp for all modules
> ------------------------------
>
>                 Key: FLINK-25868
>                 URL: https://issues.apache.org/jira/browse/FLINK-25868
>             Project: Flink
>          Issue Type: Technical Debt
>          Components: Build System
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>             Fix For: 1.16.0
>
>
> While we have many modules with stability annotations, the japicmp plugin is only run on very few (essentially just dataset/-stream + metrics-core), essentially voiding the purpose of the annotations.
> We should look into enabling the plugin for all modules.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)