[
https://issues.apache.org/jira/browse/YETUS-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15434034#comment-15434034
]
Dima Spivak commented on YETUS-445:
-----------------------------------
JACC went through some changes recently where they changed the format of the
required annotations to require full classpaths; try updating that? Also it
might be worthwhile to make the Maven build options parametrizable with
argparse if we're trying to support more than one project? Just a thought, I'll
give this a proper review tomorrow. Love the quick work, [~andrew.wang].
> 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, YETUS-445.002.patch,
> YETUS-445.003.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)
