yetus-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <>
Subject [jira] [Commented] (YETUS-445) Incorporate check_compatibility that runs Java API Compliance Checker
Date Thu, 25 Aug 2016 05:28:20 GMT


Andrew Wang commented on YETUS-445:

Regarding the licensing, we've long used JDiff (LGPL) over in Hadoop to do API diffing. IIUC
this is okay since it's not part of the release tarball, and not used by end users. Same for
HBase and Kudu using a very similar JACC script to this one.

I guess the question here is then who the "user" is for a Yetus release: an RM? a precommit
bot? the user of the software tested by Yetus? And how "optional" this functionality is.

In any case, I think it's quite unfortunate if which Apache repo a script is in determines
its legality.

> Incorporate check_compatibility that runs Java API Compliance Checker
> ---------------------------------------------------------------------
>                 Key: YETUS-445
>                 URL:
>             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, YETUS-445.004.patch,
> Kudu has a 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:

This message was sent by Atlassian JIRA

View raw message