Not sure I agree, seems like both are in java 7. http://docs.oracle.com/javase/specs/jvms/se7/html/jvms-6.html On Jan 8, 2015 3:44 AM, "Mark Struberg" <[email protected]> wrote:
> Probably I should explain the reason for forcing java7: > > If you build a lot of code with java8 the resulting jars will contain > invokevirtual, invokespecial, etc to methods from java8. And those are NOT > available in any java7 runtime. > > Thus by releasing some jar with java8 it very often cannot be used in ALL > older java versions. It will simply blow up with a NoSuchMethodException, > ValidationException, etc. Been there, done that - was pretty painful ;) > > > LieGrue, > strub > > > > > > On Thursday, 8 January 2015, 8:48, Romain Manni-Bucau < > [email protected]> wrote: > > > @Olivier: not sure I get you, if we build with j8 we can build with > > j7. We just need to ensure we don't release like it. > > > > +1 for Mark solution (toolchains in a profile and this profile 'auto' > > activated through mvn release plugin ) > > > > > > Romain Manni-Bucau > > @rmannibucau > > http://www.tomitribe.com > > http://rmannibucau.wordpress.com > > https://github.com/rmannibucau > > > > > > > > 2015-01-08 8:27 GMT+01:00 Oliver B. Fischer <[email protected]>: > >> One solution could be to put the Java 7 module in a separate profile > with > >> and active it only if you build with Java 7. > >> > >> > >> -- > >> N Oliver B. Fischer > >> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany > >> P +49 30 44793251 > >> M +49 178 7903538 > >> E [email protected] > >> S oliver.b.fischer > >> J [email protected] > >> X http://xing.to/obf > >> > > >
