Re: [DISCUSS] Brining clirr to the ASF?

2016-06-14 Thread Benedikt Ritter
gt; > From: Gary Gregory [mailto:garydgreg...@gmail.com] > > Sent: Monday, June 13, 2016 23:23 > > To: Commons Developers List <dev@commons.apache.org> > > Subject: Re: [DISCUSS] Brining clirr to the ASF? > > > > On Mon, Jun 13, 2016 at 11:19 P

RE: [DISCUSS] Brining clirr to the ASF?

2016-06-14 Thread Dennis E. Hamilton
> > Subject: Re: [DISCUSS] Brining clirr to the ASF? > > On Mon, Jun 13, 2016 at 11:19 PM, Benedikt Ritter <brit...@apache.org> > wrote: > > > Hi, > > > > as Jochen has pointed out, Clirr seems to be unmaintained. However we > build > > a go

Re: [DISCUSS] Brining clirr to the ASF?

2016-06-14 Thread Paul King
For any Gradle users, Cédric put together a little Gradle plugin based around the japicmp library which we use in Groovy, see here: https://github.com/apache/groovy/blob/master/gradle/binarycompatibility.gradle Cheers, Paul. On Tue, Jun 14, 2016 at 9:56 PM, James Carman

Re: [DISCUSS] Brining clirr to the ASF?

2016-06-14 Thread James Carman
+1 to Jochen's idea and I'd love to contribute to that effort! On Tue, Jun 14, 2016 at 2:40 AM Jochen Wiedmann wrote: > On Tue, Jun 14, 2016 at 8:23 AM, Gary Gregory > wrote: > > >> as Jochen has pointed out, Clirr seems to be unmaintained.

Re: [DISCUSS] Brining clirr to the ASF?

2016-06-14 Thread Uwe Barthel
As Clirr is internally based on BCEL, I'd rather see us build a new tool on top of ASM, which is very well maintained. Besides, that would solve the license problem. Sounds like a existing idea. I'm interested in to contribute. -- barthel

Re: [DISCUSS] Brining clirr to the ASF?

2016-06-14 Thread Jochen Wiedmann
On Tue, Jun 14, 2016 at 8:50 AM, Benedikt Ritter wrote: > Jochen Wiedmann schrieb am Di., 14. Juni 2016 >> As Clirr is internally based on BCEL, I'd rather see us build a new >> tool on top of ASM, which is very well maintained. Besides, that would

Re: [DISCUSS] Brining clirr to the ASF?

2016-06-14 Thread Benedikt Ritter
Jochen Wiedmann schrieb am Di., 14. Juni 2016 um 08:40 Uhr: > On Tue, Jun 14, 2016 at 8:23 AM, Gary Gregory > wrote: > > >> as Jochen has pointed out, Clirr seems to be unmaintained. However we > build > >> a good part of our release strategy

Re: [DISCUSS] Brining clirr to the ASF?

2016-06-14 Thread Jochen Wiedmann
On Tue, Jun 14, 2016 at 8:23 AM, Gary Gregory wrote: >> as Jochen has pointed out, Clirr seems to be unmaintained. However we build >> a good part of our release strategy upon clirr. So I wonder whether we >> should foster bringing clirr to the ASF (for example by going

Re: [DISCUSS] Brining clirr to the ASF?

2016-06-14 Thread Benedikt Ritter
Gary Gregory schrieb am Di., 14. Juni 2016 um 08:23 Uhr: > On Mon, Jun 13, 2016 at 11:19 PM, Benedikt Ritter > wrote: > > > Hi, > > > > as Jochen has pointed out, Clirr seems to be unmaintained. However we > build > > a good part of our release

Re: [DISCUSS] Brining clirr to the ASF?

2016-06-14 Thread Gary Gregory
On Mon, Jun 13, 2016 at 11:19 PM, Benedikt Ritter wrote: > Hi, > > as Jochen has pointed out, Clirr seems to be unmaintained. However we build > a good part of our release strategy upon clirr. So I wonder whether we > should foster bringing clirr to the ASF (for example by

[DISCUSS] Brining clirr to the ASF?

2016-06-14 Thread Benedikt Ritter
Hi, as Jochen has pointed out, Clirr seems to be unmaintained. However we build a good part of our release strategy upon clirr. So I wonder whether we should foster bringing clirr to the ASF (for example by going through incubation). We're probably not the only ASF project using Clirr. Benedikt