yetus-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <>
Subject [jira] [Commented] (YETUS-445) Incorporate check_compatibility that runs Java API Compliance Checker
Date Wed, 24 Aug 2016 22:35:22 GMT


Allen Wittenauer commented on YETUS-445:

* Before check in, I'd like to avoid the mistake we made with annotations and make sure this
has java in the name.... unless there is a plan to make this work with other languages/runtimes?

* [~busbey], can you help clarify the licensing rules here?  I didn't think we were allowed
to require a Category X component to get functionality? I'm thinking specifically of when
we flipped the default on test-patch such that all features were optional...

* It's interesting that JAPICC needs at least perl 5.8 installed. That's a 14 year old version.
 It's an interesting point in the python 2.6 vs. python 2.7 discussion.

> 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