Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
MIME-Version: 1.0
In-Reply-To: <CALznzY4-U1mNamp3T3KWxZY8J7erZ5dkV3QCWB1FXWojnh9iDg@mail.gmail.com>
References: <CAB917RJ53u6SjJzkEz7GWPiGrBgbQJUn2V6SCj=MgZhamekqhw@mail.gmail.com>
 <CACZkXPxeKxA=-9qX1qbuET4_Q35mECpBVD0a4DfEVd+8irDVdA@mail.gmail.com>
 <CAF8HOZKZ0qejqmnS+DraKsYMHp0pZi6U24sY+jWehzKvDV9tpA@mail.gmail.com> <CALznzY4-U1mNamp3T3KWxZY8J7erZ5dkV3QCWB1FXWojnh9iDg@mail.gmail.com>
From: Paul King <paul.king.asert@gmail.com>
Date: Tue, 14 Jun 2016 23:36:10 +1000
Message-ID: <CADRx3PPw0Lz9fKkJQc5Nvw+pKZzAm9ju-EE+m8oisi_n4mpyJg@mail.gmail.com>
Subject: Re: [DISCUSS] Brining clirr to the ASF?
To: Commons Developers List <dev@commons.apache.org>
Content-Type: multipart/alternative; boundary=94eb2c0b09b491b35805353d162a
archived-at: Tue, 14 Jun 2016 13:36:24 -0000

--94eb2c0b09b491b35805353d162a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

For any Gradle users, C=C3=A9dric 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.gra=
dle

Cheers, Paul.

On Tue, Jun 14, 2016 at 9:56 PM, James Carman <james@carmanconsulting.com>
wrote:

> +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 <jochen.wiedmann@gmail.co=
m
> >
> wrote:
>
> > On Tue, Jun 14, 2016 at 8:23 AM, Gary Gregory <garydgregory@gmail.com>
> > wrote:
> >
> > >> as Jochen has pointed out, Clirr seems to be unmaintained. However w=
e
> > 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 throug=
h
> > >> incubation). We're probably not the only ASF project using Clirr.
> > >>
> > >
> > > +1. Can we bring in code that's under GNU Lesser General Public and
> make
> > it
> > > ASL 2?
> > >
> > > Could fit under a new Commons Build or Clirr component since it is a
> > > "common" build requirement.
> >
> > 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.
> >
> > Jochen
> >
> >
> > --
> > The next time you hear: "Don't reinvent the wheel!"
> >
> >
> >
> http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/evolution=
-of-the-wheel-300x85.jpg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>

--94eb2c0b09b491b35805353d162a--