[jira] [Commented] (YETUS-445) Incorporate check_compatibility that runs Java API Compliance Checker

["Siyao Meng (Jira)" <ji...@apache.org>]

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

Siyao Meng commented on YETUS-445:
----------------------------------

Discussed today with [~weichiu] that it's best to bring API compatibility check back to upstream.

Would there be a problem if we use GPL binaries in the process? If we are only using the binaries, not including the source code, it should be fine right? Any recommendations?

> Incorporate check_compatibility that runs Java API Compliance Checker
> ---------------------------------------------------------------------
>
>                 Key: YETUS-445
>                 URL: https://issues.apache.org/jira/browse/YETUS-445
>             Project: Yetus
>          Issue Type: New Feature
>    Affects Versions: 0.3.0
>            Reporter: Andrew Wang
>            Assignee: Andrew Wang
>            Priority: Major
>         Attachments: YETUS-445.001.patch, YETUS-445.002.patch, YETUS-445.003.patch, YETUS-445.004.patch, YETUS-445.005.patch
>
>
> Kudu has a check_compatibility.py script which runs Java ACC to determine API changes between releases. HBase has a similar script written in bash, and there's also demand for using this in Hadoop.
> Rather than having this script in 3 different places, it'd be nice if it was maintained in Yetus instead. We can bring in the Kudu version as a starting point:
> https://github.com/apache/kudu/blob/master/build-support/check_compatibility.py



--
This message was sent by Atlassian Jira
(v8.3.4#803005)