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-4310) Move BinaryCompatibility Check plugin to relevant projects
Date Fri, 05 Aug 2016 10:23:20 GMT

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

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

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/2334
  
    True, the `flink-metrics-core` would not need it right now. I added it because it is somehow
part of the public API.
    
    We would need to re-add the annotations dependency - for that, let's check with the users
that requested the "project independence" if they see any problem with that.


> 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
>
> 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)

Mime
View raw message