There is also a very cool tool from the Lucene land, written by Uwe Schindler --
https://code.google.com/p/forbidden-apis/ This lets you selectively forbid certain methods from your codebase (and the default list of forbidden methods has a strong rationale to be discouraged -- locale-sensitive methods, etc.). Dawid On Fri, Nov 28, 2014 at 1:09 AM, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > On Thursday, 27 November 2014, Mark Derricutt <m...@talios.com> wrote: > >> On 28 Nov 2014, at 10:32, Igor Fedorenko wrote: >> >> > Out of curiosity, why do you want to get exactly the same bytecode? Does >> > the code compiled with java8 not work under java7? >> >> Mostly - it's due to method signature resolution. For instance in the JDK >> 5 -> 6 change, some functions that used to take `String` were changed to >> take `CharSequence` - when compiling against the JDK6 classes the byte code >> binds against `CharSequence`, thus when running under JDK5 you get >> method-not-found exceptions. >> >> > I hope animal-sniffer has your back for those cases though? > > >> >> -- >> Mark Derricutt >> http://www.theoryinpractice.net >> http://plus.google.com/+MarkDerricutt >> http://twitter.com/talios >> http://facebook.com/mderricutt >> > > > -- > Sent from my phone --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
