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 2016/08/12 13:28:20 UTC

[jira] [Closed] (FLINK-4310) Move BinaryCompatibility Check plugin to relevant projects

     [ https://issues.apache.org/jira/browse/FLINK-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler closed FLINK-4310.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.0

Implemented in e629b2e8eb21b6223335a8a0c2ff1a4d6413597b

> Move BinaryCompatibility Check plugin to relevant projects
> ----------------------------------------------------------
>
>                 Key: FLINK-4310
>                 URL: https://issues.apache.org/jira/browse/FLINK-4310
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System
>    Affects Versions: 1.1.0
>            Reporter: Stephan Ewen
>            Assignee: Stephan Ewen
>             Fix For: 1.2.0
>
>
> The Maven plugin that checks binary compatibility is currently run for every project, rather than only the once where we have public API classes.
> Since the plugin contributes to build instability in some cases, we can improve stability by running it only in the relevant projects.



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