beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ismaël Mejía (JIRA) <j...@apache.org>
Subject [jira] [Commented] (BEAM-1131) Consider japicmp for testing backwards-compatibility
Date Thu, 04 May 2017 20:14:04 GMT

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

Ismaël Mejía commented on BEAM-1131:
------------------------------------

I don't know how far are you on this one, but there is also this other backward compliance
validator:
https://github.com/lvc/japi-compliance-checker

That is the one HBase and Hadoop use, they have a tracker for multiple Java projects that
is quite nice.
https://abi-laboratory.pro/java/tracker/


> Consider japicmp for testing backwards-compatibility
> ----------------------------------------------------
>
>                 Key: BEAM-1131
>                 URL: https://issues.apache.org/jira/browse/BEAM-1131
>             Project: Beam
>          Issue Type: New Feature
>          Components: testing
>            Reporter: Kenneth Knowles
>            Assignee: Jason Kuster
>
> japicmp is what Flink uses to test backwards-compatibility, configuration here: https://github.com/apache/flink/blob/41d5875bfc272f2cd5c7e8c8523036684865c1ce/pom.xml#L1184
> At our first stable release, we should activate this plugin too! (configuration to be
determined by community discussion). We should have it installed and configured beforehand,
informational-only, so that we have a sense of it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message