Re: commons-parent: add revapi, drop clirr

[Gary Gregory]

Dropping Clirr is fine by me but adding adding another plugin to do the
same thing that JApiCmp is not (for me), it's confusing. A component can
always choose to replace JApiCmp with revapi.

Gary

On Mon, Aug 29, 2022, 05:50  wrote:

> Hi,
>
> as part of commons-csv pr 252<
> https://github.com/apache/commons-csv/pull/252> there is a discussion
> whether to add revapi-maven-plugin to commons-parent in addition to
> japicmp-maven-plugin and drop clirr-maven-plugin.
> The plugins perform checks to ensure source compatibility and binary
> compatibility of artifacts.
>
> The proposal is that japicmp and revapi co-exist in parent as together the
> tools provide better coverage than just having either one.
> Clirr is not under active maintenance any longer and will be removed.
>
> Does anyone have thoughts or objections?
>
> cheers
> Markus
>

commons-parent: add revapi, drop clirr

[sman81]

Hi,

as part of commons-csv pr 252 
there is a discussion whether to add revapi-maven-plugin to commons-parent in 
addition to japicmp-maven-plugin and drop clirr-maven-plugin.
The plugins perform checks to ensure source compatibility and binary 
compatibility of artifacts.

The proposal is that japicmp and revapi co-exist in parent as together the 
tools provide better coverage than just having either one.
Clirr is not under active maintenance any longer and will be removed.

Does anyone have thoughts or objections?

cheers
Markus