You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2016/10/06 07:38:20 UTC
[jira] [Updated] (HADOOP-13583) Incorporate checkcompatibility
script which runs Java API Compliance Checker
[ https://issues.apache.org/jira/browse/HADOOP-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wang updated HADOOP-13583:
---------------------------------
Attachment: HADOOP-13583.002.patch
Thanks for the review Robert, sloppy on my part to not test the patch before porting it from Yetus. This rev should address most, as well as Sean's nit.
On the exit code, I think we should still return non-zero when there are incompatibilities. I left this as is, but if you want I can squash the exception stack trace into just returning the exit code from JACC.
> Incorporate checkcompatibility script which runs Java API Compliance Checker
> ----------------------------------------------------------------------------
>
> Key: HADOOP-13583
> URL: https://issues.apache.org/jira/browse/HADOOP-13583
> Project: Hadoop Common
> Issue Type: Improvement
> Components: scripts
> Affects Versions: 2.6.4
> Reporter: Andrew Wang
> Assignee: Andrew Wang
> Attachments: HADOOP-13583.001.patch, HADOOP-13583.002.patch
>
>
> Based on discussion at YETUS-445, this code can't go there, but it's still very useful for release managers. A similar variant of this script has been used for a while by Apache HBase and Apache Kudu, and IMO JACC output is easier to understand than JDiff.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org