On Wed, Jun 15, 2016 at 6:45 AM, Charles Honton <c...@honton.org> wrote: > 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?
If I remember correctly, nobody rejected giving japicmp a try. 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-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
