From notifications-return-8017-archive-asf-public=cust-asf.ponee.io@yetus.apache.org Thu Oct 3 23:08:03 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id D5DAF18065B for ; Fri, 4 Oct 2019 01:08:02 +0200 (CEST) Received: (qmail 89051 invoked by uid 500); 3 Oct 2019 23:08:02 -0000 Mailing-List: contact notifications-help@yetus.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@yetus.apache.org Delivered-To: mailing list notifications@yetus.apache.org Received: (qmail 89041 invoked by uid 99); 3 Oct 2019 23:08:02 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Oct 2019 23:08:02 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 88EE0E3118 for ; Thu, 3 Oct 2019 23:08:01 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 270277807D9 for ; Thu, 3 Oct 2019 23:08:00 +0000 (UTC) Date: Thu, 3 Oct 2019 23:08:00 +0000 (UTC) From: "Siyao Meng (Jira)" To: notifications@yetus.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YETUS-445) Incorporate check_compatibility that runs Java API Compliance Checker MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)