commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul King <paul.king.as...@gmail.com>
Subject Re: [DISCUSS] Brining clirr to the ASF?
Date Tue, 14 Jun 2016 13:36:10 GMT
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 <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.com
> >
> 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 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.
> > >>
> > >
> > > +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
> >
> >
>

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