You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2016/08/23 22:51:22 UTC
[jira] [Updated] (YETUS-445) Incorporate check_compatibility that
runs Java API Compliance Checker
[ https://issues.apache.org/jira/browse/YETUS-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wang updated YETUS-445:
------------------------------
Attachment: YETUS-445.001.patch
Here's a quick port of the Kudu script to be a little less Kudu specific. I tested it on a small Java project I have lying around.
This script is less featureful than the HBase version. I also had to hack out a bunch of Kudu-specific build code to make this work; Kudu did this since they have a single repo with both C++ and Java code, and wanted to avoid copying all the C++ code twice, and also handle "mvn package" not working in the root of the directory.
Let's see what precommit says, chances are pylint will have a field day.
> 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
> Attachments: YETUS-445.001.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
(v6.3.4#6332)