Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
From: Stefan Bodewig <bodewig@apache.org>
To: Gilles <gilles@harfang.homelinux.org>
Cc: <dev@commons.apache.org>
Subject: Re: [all] Clirr or japicmp - does either work for anybody?
References: <877f6umx4d.fsf@v45346.1blu.de>
	<72a79f25c63d7edac6276e34a6c11641@scarlet.be>
Date: Thu, 22 Dec 2016 08:18:23 +0100
In-Reply-To: <72a79f25c63d7edac6276e34a6c11641@scarlet.be>
	(gilles@harfang.homelinux.org's message of "Wed, 21 Dec 2016 15:36:35
	+0100")
Message-ID: <8737hgwhxc.fsf@v45346.1blu.de>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
archived-at: Thu, 22 Dec 2016 07:18:27 -0000

On 2016-12-21, Gilles wrote:

> On Tue, 20 Dec 2016 16:35:46 +0100, Stefan Bodewig 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).

> In Commons RNG, running
>  $ mvn clean site site:stage
> will generate the Clirr report(s).  See e.g. in
>   target/staging/commons-rng-simple/clirr-report.html

> [Building with Java 8 here.]

Strange, doesn't seem to work for me. Anyway, I've now switched to use
jacoco and got japicmp to work (will start a new thread for potential
changes to the parent pom).

Thanks

        Stefan

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