commons-parent has two plugins "doing the same thing": japicmp and clirr
We drop the one that does not work / is unmaintained and not future-proof (clirr) and replace it by revapi. Still two plugins. Rather than doing the same thing, these plugins complement each other - kind of like Checkstyle and PMD: large overlap yet they produce findings the other one does not. japicmp has failed to recognize a recent incompatible API change in csv-commons that revapi spots (CSV-302<https://issues.apache.org/jira/projects/CSV/issues/CSV-302>) therefore brushing off revapi is not a good solution (to me). At the same time there might be scenarios where japicmp beats revapi. cheers Markus ________________________________ From: Gary Gregory <garydgreg...@gmail.com> Sent: Monday, August 29, 2022 12:28 To: Commons Developers List <dev@commons.apache.org> Subject: Re: commons-parent: add revapi, drop clirr 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 <sma...@outlook.de> 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 >
