I would choose Java 1.8 all the way if you have to choose. I would do this because this is going to be a long standing maintenance release. Just a note, the Eclipse neon out in June will require Java 1.8. I think it makes sense to upgrade. I think folks can go through the pain of upgrading there servlet containers to Java 1.8 if they want to move forward.
On Friday, February 12, 2016 at 8:39:41 AM UTC-8, Colin Alworth wrote: > > Switching to gwt-contrib, we're losing voices who are involved in this > discussion. > > Maybe I am missing something, but I had that that the discussion moved > toward the fact that the compiler and dev mode will require Java8, but that > gwt-servlet could still be compiled to Java7, allowing deployment on Java7. > > The supersource classes do require Java8 language level in the GWT > compiler (in order to have "default" mean anything), but these emulation > classes are not compiled to bytecode, and not required to compile the rest > of GWT. > > We already have cases where GWT will not work without Java8 (specifically > Dev Mode and anything that leans on it), so this isn't a change from the > beta. I agree with Daniel that effort will be required to compile to Java7 > bytecode (as previously discussed), and while I would be interested in > helping to achieve this, we've also clearly stated that Java8 support is a > more important goal (both in terms of keeping GWT modern and up to date in > the Java world, but also in terms of staying relevant for web development > with lambdas and JSInterop). > > Even if we manage to compile to Java7 bytecode from a Java8 JDK, it has > been encouraged that we extensively test to ensure that all of the code > does as we expect, as regressions have been seen in the past. RetroLambda > was another suggestion that also may have merit. > > On Fri, Feb 12, 2016 at 10:28 AM Daniel Kurka <[email protected] > <javascript:>> wrote: > >> GWT 2.8 needs to contain Java8 APIs so taht guava will start working >> again. All the outstanding Java8 patches need to go in before 2.8. So 2.8 >> will not work with Java7. >> >> >> On Fri, Feb 12, 2016 at 5:25 PM Jens Nehlmeier <[email protected] >> <javascript:>> wrote: >> >>> Its not just about adding new classes but we also add APIs to existing >>> classes that require Java8 classes in their signature. So you would >>> need to ignore these changes on method level. >>> >>> AFAICT it was said that as soon as Java 8 APIs are committed GWT will >>> require Java8. If someone needs Java7 support they need to replace the >>> emulation code of GWT 2.8 with the one of GWT 2.7. Because of this >>> possibility we don't use Java8 APIs in gwt-user code. gwt-servlet.jar >>> is something to think about as soon as we want to add GWT-RPC >>> serializer for Java 8 classes. If we really want to give users the >>> possibility to compile GWT 2.8 with Java 7 after replacing the >>> emulation code we probably need a build target that builds >>> gwt-servlet-jdk8.jar when running Java8 only. >>> >>> Generally I thought Java8 stuff will be committed after GWT 2.8 has >>> been released so that GWT 2.8 stays Java7 compatible. I don't know >>> about the Guava issue that requires GWT 2.8 to already have Java8 APIs >>> available. I thought Guava will just release Guava 20 when 2.8 is >>> released because Gauva 19 did use some private APIs of GWT that do not >>> exist anymore. >>> >>> >>> >>> 2016-02-12 16:06 GMT+01:00 Daniel Kurka <[email protected] >>> <javascript:>>: >>> > +Colin Alworth +Jens >>> > >>> > Colin and Jens have been doing a lot of the Java8 API work, I believe >>> this >>> > will touch many classes within the JRE and thus will not be as easy as >>> > ignoring a few classes. >>> > >>> > To be clear: >>> > We won't be putting any resources into addressing this since its not an >>> > issue for us, if someone feels strongly (s)he can step up and tackle >>> this, >>> > but the whole case does not seem to be convincing for me, why would >>> agencies >>> > that are slow to adopt things adopt the latest GWT version? >>> > >>> > -Daniel >>> > >>> > On Fri, Feb 12, 2016 at 3:52 PM Manuel Carrasco Moñino < >>> [email protected] <javascript:>> >>> > wrote: >>> >> >>> >> Well the situation I know, is that there are many big companies and >>> >> government agencies moving very slow, their standard server >>> configuration is >>> >> java7, as well as their code standards. >>> >> >>> >> Their GWT projects are compiled in one phase (not client and server >>> >> sides). It could be very difficult for them to compile their byte >>> code for >>> >> 1.7. >>> >> It's true that if they don't use java 8 many features in 2.8 are >>> useless >>> >> for them, but we have to facilitate and encourage users to be in >>> latest >>> >> version. >>> >> >>> >> I don't know how complex it could be, but if for example, ignoring >>> java8 >>> >> /emul/ classes could fix the problem I think it's worth to consider. >>> >> >>> >> On Fri, Feb 12, 2016 at 3:42 PM, 'Daniel Kurka' via gwt-maintainers >>> >> <[email protected] <javascript:>> wrote: >>> >>> >>> >>> I am not sure how this is connected to the beta1 release. Beta1 did >>> not >>> >>> have any Java8 apis for the final release we need them to support >>> the next >>> >>> version of guava. >>> >>> >>> >>> If you feel strongly you can always step in with a design that will >>> >>> support both modes and execute on it, but we went over this in the >>> SC and >>> >>> this seems like a lot of work for something that almost all devs are >>> fine >>> >>> with (run java8 while developing). >>> >>> >>> >>> >>> >>> On Fri, Feb 12, 2016 at 3:36 PM Manuel Carrasco Moñino >>> >>> <[email protected] <javascript:>> wrote: >>> >>>> >>> >>>> Since beta1 supports 1.7, isn't feasible someway to make the >>> compiler >>> >>>> ignore java8 specific stuff when compiler level is set to java 7? >>> >>>> >>> >>>> On Fri, Feb 12, 2016 at 3:29 PM, 'Daniel Kurka' via gwt-maintainers >>> >>>> <[email protected] <javascript:>> wrote: >>> >>>>> >>> >>>>> Compiling GWT code will require Java 8, if someone is willing to >>> put in >>> >>>>> the work we can potentially make GWT servlet run in java7 >>> >>>>> >>> >>>>> >>> >>>>> On Fri, Feb 12, 2016, 3:18 PM Manuel Carrasco Moñino >>> >>>>> <[email protected] <javascript:>> wrote: >>> >>>>>> >>> >>>>>> Is it planed to be fixed? or do we break 1.7 compatibility ? >>> >>>>>> >>> >>>>>> On Fri, Feb 12, 2016 at 3:16 PM, 'Daniel Kurka' via >>> gwt-maintainers >>> >>>>>> <[email protected] <javascript:>> wrote: >>> >>>>>>> >>> >>>>>>> This is expected since java8 emulation patches have gone in. >>> >>>>>>> >>> >>>>>>> On Fri, Feb 12, 2016 at 3:11 PM Manuel Carrasco Moñino >>> >>>>>>> <[email protected] <javascript:>> wrote: >>> >>>>>>>> >>> >>>>>>>> >>> >>>>>>>> >>> >>>>>>>> Current master seems not supporting correctly compilation in >>> java , >>> >>>>>>>> take a look to CI output when compiling dynatablerf which is >>> configured to >>> >>>>>>>> be compiled in 1.7 mode >>> >>>>>>>> >>> >>>>>>>> http://build.gwtproject.org/job/gwt-samples/15/console >>> >>>>>>>> >>> >>>>>>>> -- >>> >>>>>>>> You received this message because you are subscribed to the >>> Google >>> >>>>>>>> Groups "gwt-maintainers" group. >>> >>>>>>>> To unsubscribe from this group and stop receiving emails from >>> it, >>> >>>>>>>> send an email to [email protected] >>> <javascript:>. >>> >>>>>>>> For more options, visit https://groups.google.com/d/optout. >>> >>>>>>> >>> >>>>>>> -- >>> >>>>>>> You received this message because you are subscribed to the >>> Google >>> >>>>>>> Groups "gwt-maintainers" group. >>> >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>> >>>>>>> send an email to [email protected] <javascript:> >>> . >>> >>>>>>> For more options, visit https://groups.google.com/d/optout. >>> >>>>>> >>> >>>>>> >>> >>>>> -- >>> >>>>> You received this message because you are subscribed to the Google >>> >>>>> Groups "gwt-maintainers" group. >>> >>>>> To unsubscribe from this group and stop receiving emails from it, >>> send >>> >>>>> an email to [email protected] <javascript:>. >>> >>>>> For more options, visit https://groups.google.com/d/optout. >>> >>>> >>> >>>> >>> >>> -- >>> >>> You received this message because you are subscribed to the Google >>> Groups >>> >>> "gwt-maintainers" group. >>> >>> To unsubscribe from this group and stop receiving emails from it, >>> send an >>> >>> email to [email protected] <javascript:>. >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >>> >> >>> > >>> >>> >>> >>> -- >>> Mit freundlichen Grüssen >>> >>> Jens Nehlmeier >>> >> -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/deb945ab-0dba-4f6a-93b6-9547da086cdc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
