flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3129) Add tooling to ensure interface stability
Date Mon, 21 Mar 2016 09:34:25 GMT

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

ASF GitHub Bot commented on FLINK-3129:
---------------------------------------

Github user rmetzger commented on the pull request:

    https://github.com/apache/flink/pull/1791#issuecomment-199192415
  
    I rebased the change to the latest master.
    I'm currently discussing with the author of the maven plugin if we can make it accept
the removal of the `Key` interface.


> Add tooling to ensure interface stability
> -----------------------------------------
>
>                 Key: FLINK-3129
>                 URL: https://issues.apache.org/jira/browse/FLINK-3129
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Build System
>            Reporter: Robert Metzger
>            Assignee: Robert Metzger
>
> I would like to use this maven plugin: https://github.com/siom79/japicmp to automatically
ensure interface stability across minor releases.
> Ideally we have the plugin in place after Flink 1.0 is out, so that maven builds break
if a breaking change has been made.
> The plugin already supports downloading a reference release, checking the build and breaking
it.
> Not yet supported are class/method inclusions based on annotations, but I've opened a
pull request for adding it.
> There are also issues with the resolution of the dependency with the annotations, but
I'm working on resolving those issues.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message