Re: [gwt-contrib] Re: GWT 2.7 requiring Java7 for development - Action needed

2014-09-12 Thread 'Daniel Kurka' via GWT Contributors 
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

On Fri, Sep 12, 2014 at 12:14 AM, Artur Signell  wrote:

> 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
>
> On Thursday, September 11, 2014 8:50:53 PM UTC+3, Daniel Kurka wrote:
>>
>> 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
>>
>  --
> 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-contributors+unsubscr...@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

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujiqWK7Zv6DakhsOWw-z%2BOUt3pRx1C%3DRXdbvMdWWgpZZwzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Vaadin and GWT 2.7 compilePerFile

2014-09-12 Thread 'John Stalcup' via GWT Contributors 
Just to close the loop on the conversation, this is fixed in
https://gwt-review.googlesource.com/#/c/9131/

Thanks for the report Artur.

On Wed, Sep 10, 2014 at 9:06 AM, John Stalcup  wrote:

> Ah, i didn't see that bug report. Thanks. Taking a look.
>
> On Wed, Sep 10, 2014 at 12:36 AM, Artur Signell  wrote:
>
>> Hi,
>>
>> There is some issue with -XcompilerPerFile and the generators used in
>> Vaadin. There was a problem with  “stale types” previously, but this was
>> fixed a while back. Today you consistently get a ClassCastException after
>> the first partial recompilation.
>>
>> SEVERE: undefinedjava.lang.ClassCastException
>> at Unknown.Throwable_1_g$(com.vaadin.DefaultWidgetSet-0.js@8:8546)
>> at Unknown.Exception_1_g$(com.vaadin.DefaultWidgetSet-0.js@18:8704)
>> at Unknown.RuntimeException_1_g$(com.vaadin.DefaultWidgetSet-0.js@18:8745)
>> at 
>> Unknown.ClassCastException_1_g$(com.vaadin.DefaultWidgetSet-0.js@25:154772)
>> at Unknown.dynamicCast_0_g$(com.vaadin.DefaultWidgetSet-0.js@11:600)
>> at Unknown.createWidget_0_g$(com.vaadin.DefaultWidgetSet-0.js@12:102047)
>> at Unknown.getWidget_7_g$(com.vaadin.DefaultWidgetSet-0.js@29:102094)
>>
>> I don’t have any good way of extracting a small test case so I created
>> https://code.google.com/p/google-web-toolkit/issues/detail?id=8880 already
>> a while back with instructions on how it can be reproduced using the Vaadin
>> project.
>>
>> Would be great to get this sorted out before GWT 2.7 - is there anything
>> I can do to help getting this forward?
>>
>> - Artur
>> --
>> Artur Signell, CTO
>> Vaadin.com - +358 40 567 0089 - Skype:artursignell
>>
>>  --
>> 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-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CBDB0261-D4A0-470B-8538-089C89F1D598%40vaadin.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAFw3gJ-5i3CjufC3p_B5B8zZE2T08G%3DrQueeXAGRCnJ3a2cqDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Configurable checks for GWT

2014-09-12 Thread 'Goktug Gokdogan' via GWT Contributors 
I have a patch that will introduce a preconditions helper class to be used
internally by the SDK. It will be very similar to the one in Guava with
some modifications.

My goals with this class are:
 1- Ability to provide different levels of checking (e.g. development vs
production) without worrying about code size or performance.
 2- Improve code readability across the SDK.

Here is the quick design doc:
https://docs.google.com/document/d/1AegOijkqg9ix6wtMMPYU0JeDBZXIzSgopDifPV7gH9E/edit?usp=sharing

Please feel free to comment. I'll be on vacation next week and will
probably respond the other week.

Thanks,

- Goktug

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA0Hapm3pKDc71Kee3R4-neB6Kv%2BnvJ2eF0UE__FsHR0Ow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT 2.7 requiring Java7 for development - Action needed

2014-09-12 Thread 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

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/acf892ed-c0b8-4ad2-b74c-7a57e04928b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT 2.7 requiring Java7 for development - Action needed

2014-09-12 Thread 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.

Am Donnerstag, 11. September 2014 19:50:53 UTC+2 schrieb 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
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/a054c77d-725e-4559-9a35-441c2b416387%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT 2.7 requiring Java7 for development - Action needed

2014-09-12 Thread 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

On Thursday, September 11, 2014 8:50:53 PM UTC+3, Daniel Kurka wrote:
>
> 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
>

-- 
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-contributors+unsubscr...@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.

Re: [gwt-contrib] Re: GWT 2.7 requiring Java7 for development - Action needed

2014-09-12 Thread 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.

On Fri, Sep 12, 2014 at 6:23 AM, Mohammed  wrote:

> I think its fine we require Java 7 for GWT 2.7
>
> On Thursday, September 11, 2014 11:20:53 PM UTC+5:30, Daniel Kurka wrote:
>>
>> 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
>>
>  --
> 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-contributors+unsubscr...@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
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABrJHW2mx%3DbAv%3DFbhg-HkZfydFVTJgXcPLSfaPd-%2BooPKfYeBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.