commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gilles <gil...@harfang.homelinux.org>
Subject Re: [rng] japicmp failure
Date Wed, 02 May 2018 10:10:24 GMT
On Tue, 1 May 2018 17:05:23 -0400, Rob Tompkins wrote:
> I was starting to fiddle with [parent] version 46 with [rng] and
> stumbled across the seemingly legitimate japicmp failure. @Gilles -
> any thoughts here? If it is indeed correct I would think those would
> be BC incompatible changes between 1.0 and 1.1.
>
> -Rob
>
> Comparing source compatibility of commons-rng-core-1.1-SNAPSHOT.jar
> against commons-rng-core-1.0.jar
> ===! UNCHANGED CLASS: PUBLIC ABSTRACT
> org.apache.commons.rng.core.source32.AbstractWell  (not serializable)
>    ===  CLASS FILE FORMAT VERSION: 50.0 <- 50.0

What is meant by the above?

> ***  MODIFIED CLASS: PUBLIC ABSTRACT
> org.apache.commons.rng.core.source32.IntProvider  (not serializable)
>    ===  CLASS FILE FORMAT VERSION: 50.0 <- 50.0
>    ---  REMOVED METHOD: PUBLIC(-) ABSTRACT(-) int next()
> ***  MODIFIED CLASS: PUBLIC ABSTRACT
> org.apache.commons.rng.core.source64.LongProvider  (not serializable)
>    ===  CLASS FILE FORMAT VERSION: 50.0 <- 50.0
>    ---  REMOVED METHOD: PUBLIC(-) ABSTRACT(-) long next()

According to Clirr, those are not BC errors:
   
http://commons.apache.org/proper/commons-rng/commons-rng-core/clirr-report.html

Best,
Gilles


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message