GWT 2.7 requiring Java7 for development - Action needed

[Daniel Kurka]

Hi all,

while bringing GSS support into GWT, I discovered that the closure styleheets compiler actually requires Java7.

This means that we either have to do a back port of the compiler (I haven't looked at it seriously) or require Java7 for development with GWT (probably only if you are using CssResource).

I really like your input on this and if I do not hear any strong objections, I will go ahead with using the Java7 version of closure stylesheets and thus we will require Java7 for GWT development.

Note: This does not impact deployment of any GWT apps. You can still run a GWT app on a Java6 container, this will only affect developers on their machines.

-Daniel

[Koen Maes]

Java7 is just fine for me...

[Christian Kütbach]

I think Jave 7 and JRE7 is fine.

Java 6 is out of public support since Feb 2013:

https://blogs.oracle.com/henrik/entry/java_6_eol_h_h

Christian

[Thomas Broyer]

I think we were OK with 2.6 being the last to support Java 6 (and erroneously released 2.6.0 compile as Java 7)

[Juan Pablo Gardella]

Java7 is fine for development 

--
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 google-web-toolkit-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/50627301-f84d-4cdd-888a-8db96d387b86%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Matic Petek]

GWT must go forward. 2.7 Java 7, 3.0 Java 8. Specially when it only effect development environment.

Regards,

  Matic

On Thursday, September 11, 2014 7:50:53 PM UTC+2, Daniel Kurka wrote:

[Alberto Mancini]

Hi,
IMHO, java 7 for development more than OK.

Thank you !

Alberto.

--

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 google-web-toolkit-co...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujip-hsvuE7-NghZGJ0HL007yjCaE5mMX2126Gag4KUJ7Ug%40mail.gmail.com.

[Brandon Donnelson]

So far I don't see any problems with the upgrade path. Those who can't jump to 2.7 can stick with 2.6 until they're ready. With the backport feature running SDM should help with that in IDES for the slow movers. I like the idea of Java 7 for 2.7. 

Brandon

[Andy Stevko]

+1 on moving to java 7

--

[Manuel Carrasco Moñino]

+1 to java7

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CANKsVVkcWHKMuCBkAcqAAWj1DU0AfkHp3PGn%2B7atR4XG5yqKQQ%40mail.gmail.com.

[Mohammed]

I think its fine we require Java 7 for GWT 2.7

[Jan Thewes]

Ok so I'm the only one how thinks this might be a problem for us.

We're using GWT in a real large company environment (core banking system) and to create a baseline we have to use our companies build server. These are currently running on Java6. I've already reached out to get an information when the Java compile level will be increased.

This is just my opinion speaking for a real large company.

[David]

No problem, we are on Java 7 for quite some time. I would not even object to Java 8 for the client side only, but I guess that can wait for 3.0. GWT/GUI development is really screaming for lambda's with all the event handling and async callbacks.

--

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 google-web-toolkit-co...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/904f4a86-630c-4d15-bf39-3b146f3db462%40googlegroups.com.

[Artur Signell]

Hi, 

Even though most people have moved to Java 7 already there is still some interest in using Java 6. As this closure compiler version would be the sole reason for requiring Java 7, I would be interested in putting in some effort to see if we can get the lastest closure compiler backported to Java 6. This would keep GWT 2.x compatible with Java 6 and leave the breaking change for GWT 3.x.

Daniel, are you looking to use the latest master or v20140814?

- Artur

[Thomas Broyer]

On Thursday, September 11, 2014 8:26:37 PM UTC+2, Christian Kütbach wrote:

Java 6 is out of public support since Feb 2013:

https://blogs.oracle.com/henrik/entry/java_6_eol_h_h

There are other JDKs than the one from Oracle.

OpenJDK 6 is still supported for instance (under the leadership of RedHat): http://www.redhat.com/en/about/press-releases/red-hat-reinforces-java-commitment-and-assumes-leadership-openjdk-6-community

This EOL is also only about public releases; you can buy support from Oracle and get up to an indefinite support for Java 6 or even 5.0: http://www.oracle.com/technetwork/java/eol-135779.html

[Daniel Kurka]

Hi Arthur,

I am actually using an internal version of the css parser (which has not been mirrored out yet), I needed to do this cause we needed to fix bugs in it in order to pass our build.

-Daniel

--

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 google-web-toolkit-co...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/3b08903c-7ee9-4d4a-9b4e-1f2cabd78b59%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Google Germany GmbH

Dienerstr. 12
80331 München

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Katherine Stephens