commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: [all] Clirr or japicmp - does either work for anybody?
Date Tue, 20 Dec 2016 21:18:20 GMT
I am not sure Clirr is maintained at all.

G

On Dec 20, 2016 8:43 AM, "Matt Benson" <gudnabrsam@gmail.com> wrote:

> I used japicmp with the last [weaver] release. Also it seems more actively
> maintained than Clirr so it would probably be easier to get a fix in.
>
> Matt
>
> On Tue, Dec 20, 2016 at 9:35 AM, Stefan Bodewig <bodewig@apache.org>
> wrote:
>
> > Hi
> >
> > I'm trying to figure out how to get a report on API changes in
> > compress.
> >
> > If I enable Clirr the site build dies with a NullPointerException (I
> > vaguely recall it might work if I used Java7, so that might by my last
> > resort).
> >
> > If I enable japicmp it dies because it thinks it has found binary
> > incompatibilities. What it has found are changes introduced by Cobertura
> > as japicmp looks at the instrumented classes. Also it seems wrong to me
> > to break the build rather than creating a report (I've tried to override
> > breakBuildOnBinaryIncompatibleModifications, but it ignores my
> > configuration).
> >
> > Would it work if I switched to Jacoco rather than Cobertura?
> >
> > Has anybody gotten either of the two to work lately?
> >
> > Stefan
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message