Hello Charles, as I said in response to Jochen, I'm fine with giving japicmp a try. But for tools as important to us as clirr, I've come to the conclusion that it would be better to have them at the ASF.
Benedikt Charles Honton <c...@honton.org> schrieb am Mi., 15. Juni 2016 um 06:45: > According to clirr-maven-plugin pom, it depends on > net.sf.clirr:chirr-core:0.6 (released on 11-Feb-2006) > org.apache.bcel:bel:5.2 (release on 13-Jun-2006) > net.sf.clirr:chirr-core:0.6 had an excluded dependency on bcel:bel:5.1 > (released 22-Nov-2005 and modified 20-Oct-2010) > > > Yes, japicmp has single developer and nine contributors. However, that > single developer has done a great job keeping up to date. Japicmp is > Apache licensed <https://github.com/siom79/japicmp/blob/master/LICENSE>. > (Clirr does not mention any license in pom) Should Martin Mois decide to > quite maintenance, the code is available both at GitHub < > https://github.com/siom79/japicmp> and Maven Central < > http://repo1.maven.org/maven2/com/github/siom79/japicmp/japicmp/0.8.0/>. > (Clirr source jar is not at Maven Central) > > Why do we find it so hard to take components or tools off the shelf? Why > are we jumping to invest time re-writing when our efforts could better be > spent on our focus products? > > regards, > chas > > > > On Jun 13, 2016, at 11:20 PM, Gary Gregory <garydgreg...@gmail.com> > wrote: > > > > On Mon, Jun 13, 2016 at 11:18 PM, Benedikt Ritter <brit...@apache.org> > > wrote: > > > >> Jochen Wiedmann <jochen.wiedm...@gmail.com> schrieb am Di., 14. Juni > 2016 > >> um 08:14 Uhr: > >> > >>> On Tue, Jun 14, 2016 at 8:11 AM, Benedikt Ritter <brit...@apache.org> > >>> wrote: > >>> > >>>> Charles Honton <c...@honton.org> schrieb am Di., 14. Juni 2016 um > >> 07:29 > >>> Uhr: > >>>> > >>>>> Now that lang is compiled with java6, clirr is broken. Do we want to > >>>>> update to a more modern report like japicmp < > >>>>> https://siom79.github.io/japicmp/>? > >>>>> > >>>> > >>>> The site build is only broken when build with Java 8. It should be > >>> working > >>>> with Java 6 and Java 7. > >>> > >>> Lets give the new kid on the block a try. (But don't forget, to > >>> report, what the experiences are.) > >>> > >> > >> okay > >> > >> > >>> > >>> Clirr is basically unmaintained, since years. A replacement would > >>> definitely be valuable. > >>> > >> > >> Could happen to japicmp sooner or later, since it seems to be > maintained by > >> a single person at the moment. I don't like pulling in dependencies like > >> this. But you're right if Clirr is unmaintained. > >> > > > > The Clirr Maven plugin is maintained though and there has been talk of > it's > > dependency on BCEL being updated. > > > > I've not looked under the plugin's hood but if the plugin is fiddling > with > > BCEL then perhaps it is doing in more than just wrapping Clirr? > > > > Gary > > > > > >> Benedikt > >> > >> > >>> Jochen > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > >>> For additional commands, e-mail: dev-h...@commons.apache.org > >>> > >>> > >> > > > > > > > > -- > > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > > Java Persistence with Hibernate, Second Edition > > <http://www.manning.com/bauer3/> > > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > > Spring Batch in Action <http://www.manning.com/templier/> > > Blog: http://garygregory.wordpress.com > > Home: http://garygregory.com/ > > Tweet! http://twitter.com/GaryGregory > >
