On Wed, Oct 9, 2013 at 4:50 PM, Emmanuel Bourg <ebo...@apache.org> wrote: > Le 09/10/2013 19:33, Gary Gregory a écrit : > >> - There is no Clirr report which makes it impossible to determine if >> binary compatibility has been preserved or broken. I do not think I >> can vote without this report. > > I generated a compatibility report with the Java API Compliance Checker: > > http://people.apache.org/~ebourg/JCI-1.1RC1/compat_report.html > > Some comments on the results: > > - Most of the incompatibilities are related to the removal of the javac > compiler (FileInputStreamProxy, FileOutputStreamProxy, Javac*) > > - The public constructors of JaninoCompilationProblem changed, this > class shouldn't be instantiated outside of JCI so the impact is negligible.
Wow, 54 removed methods in org.apache.commons.jci.compilers, that is not one method gone in some corner of an impl class. The simple and safe route is to go with a 2.0 release and be done with it. Otherwise, this will just create jar hell for unsuspecting souls in who knows what dependency chains. Gary > > Emmanuel Bourg > > > --------------------------------------------------------------------- > 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 JUnit in Action, Second Edition Spring Batch in Action Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
