Jetty 9 before RC1?

Since there are no roadblocks (htmlunit has been updated for jetty 9), is it possible for gwt to update to jetty 9? -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email

Re: How to enable two page GWT application

Thanks Jens. I will prefer the separate project. The pros are I don't need to take care about the interaction of those two pages or the tricks to make one app to act as two. The cons are I need to build and test two of them each time when coding. -- You received this message because you are

Re: native JsType with constants

>From >https://groups.google.com/d/msg/google-web-toolkit-contributors/q_GY4SxGQ7I/KrExmCQ9EgAJ > I think you need to annotate those constant fields with @JsOverlay. Or maybe you could declare them non-final and have them mapped to the native constants ($wnd.Node.ELEMENT_NODE, etc.) On

Re: Teavm

there is an old group post that already discusses the byte-code vs. source code issue - maybe it is still helpful I think the http://www.gwtproject.org/makinggwtbetter.html page should be

Re: Teavm

On Thursday, December 3, 2015 at 12:24:38 PM UTC+1, Martin Trummer wrote: > > there is an old group post > > > that already discusses the byte-code vs. source code issue - maybe it is > still

Re: native JsType with constants

Awesome. Thank you. @JsOverlay did the trick. Den torsdag den 3. december 2015 kl. 12.58.26 UTC+1 skrev Thomas Broyer: > > From > https://groups.google.com/d/msg/google-web-toolkit-contributors/q_GY4SxGQ7I/KrExmCQ9EgAJ > > I think you need to annotate those constant fields with @JsOverlay. >

Re: Teavm

> That said, browser-specific permutations has IMO reached a dead-end: > Microsoft will stop support IE<11 in 40 days or so (except IE9 on Vista), > which means that we'll have (hopefully) almost everyone using a "modern > browser" where discrepancies aren't that many and can be dealt with at >

Re: [gwt-contrib] Samples .css issue?

If you provide both the .css and .gss versions of a file. The GssResourceGenerator is smart enough to use the gss version of the file when gss is enabled even if you specify the css version in the @Source annotation. GSS is still disabled by default, so we have to keep the backward compatibility.

Re: GWT 2.8.0 RC1

A month has passed... any news? On Thursday, 5 November 2015 19:49:05 UTC+1, steve Zara wrote: > > As 2.8.0 RC1 is out this week, would it be possible to say where this will > be linked to on the GWT site? I'm not a maven user, so a link to the zip > would be helpful. > -- You received

Re: GoogleBot is using the wrong permutation?

What I did that probably solved it:​ instead of reading the permutation name through the HTTP header using RpcRequestBuilder.STRONG_NAME_HEADER, I now send the permutation name along from with the exception occurred in the client. At least I am not using any old cached http header. Let's see if

how to apply servlet chain i.e. filter etc when I invoke a servlet from GWTTestCase ?

Hi everybody, I have a GWTTestCase that needs to fetch some JSON produced on the server and use in a test. Though I have unit tests to validate everything else I am trying to write an end to end test as a GWTTestCase since it will also allow me to debug my client side code. When I invoke a

Re: how to apply servlet chain i.e. filter etc when I invoke a servlet from GWTTestCase ?

On Thursday, December 3, 2015 at 9:21:17 AM UTC+1, gau...@ainosoft.com wrote: > > Hi everybody, > > I have a GWTTestCase that needs to fetch some JSON produced on the server > and use in a test. > > Though I have unit tests to validate everything else I am trying to write > an end to end

native JsType with constants

Hi How can I add constants to a native @JsType? I was trying to add support for constants to my WebIDL to JsInterop generator but I have a problem with constants. Here is a snippet of the definition of Node [Exposed=Window] interface Node : EventTarget { const unsigned short ELEMENT_NODE =

Re: [gwt-contrib] GWT Maven Samples update for GWT 2.8

GSS is not turned on by default because we want that people migrate to GWT 2.8 without being blocked by the GSS migration. As I said in my previous mail, the compiler is smart enough to choose the right resource file (if both are provided) depending wether GSS is enabled or not. If you find a .css

Re: native JsType with constants

Ignoring initialization is quite complicated when you put in to account generated clinit and also primitives which becomes compile-time-constants per jls and automatically inlined. Also code wise it is quite weird and potentially confusing. Workaround is quite simple, just remove the "final"

Re: Teavm

I do not know if permutations have reached a dead-end but i find that 'static' (in the sense related to the browser user agent) detection is going to be hard to maintain. Each new version of a browser (and the update is largely automatic) may change the support so compiling for a specific user

Re: native JsType with constants

> Awesome. Thank you. @JsOverlay did the trick. > But IMHO @JsOverlay is only a workaround because it is meant to be used for code additions that do not exist in the underlying native type. So in your case GWT will now generate some additional code for your constants and will not use

Re: Teavm

I don't see how you can easily support and maintain something like web-components (where different Browsers implement different parts of the spec) using browser specific permutations. With Edge almost all browsers vendor follow a relatively fast release cycle (ok Safari is the new IE in this

Re: GWT 2.8.0 RC1

I've been using the 2.8.0-SNAPSHOT artifact from the https://oss.sonatype.org/content/repositories/google-snapshots/ repo for a few weeks now. We had a minor hiccup the other day but now everything is back to running smoothly. Watch out for Guava incompatibility. E On Thursday, December 3,

Re: GWT 2.8.0 RC1

AFAICT, it's coming: http://www.gwtproject.org/release-notes.html On Thursday, December 3, 2015 at 5:15:19 PM UTC+1, Michael Joyner wrote: > > Would someone please post an RC that won't break overnight BEFORE y'all > start posting possible breaking changes? > > > On 12/03/2015 10:11 AM, Thomas

Re: GWT 2.8.0 RC1

Would someone please post an RC that won't break overnight BEFORE y'all start posting possible breaking changes? On 12/03/2015 10:11 AM, Thomas Broyer wrote: FYI, we've merged back the change that splitted jsinterop annotations out

Re: GWT 2.8.0 RC1

FYI, we've merged back the change that splitted jsinterop annotations out of gwt-user; it just failed to deploy for some reason (failed early this time, so something has been deployed at all) but we might possibly have broken the snapshots again (despite tests on two independent developer

Re: GWT 2.8.0 RC1

The https://github.com/gwtproject/gwt/issues/9074 was in master. Somebody know how to check if it will be included in 2.8 release? the commit is https://github.com/gwtproject/gwt/commit/dd215d81ce29db42b185ffa2f86f6af36076f3be On 3 December 2015 at 11:06, Thomas Broyer

Re: GWT 2.8.0 RC1

> The https://github.com/gwtproject/gwt/issues/9074 was in master. Somebody > know how to check if it will be included in 2.8 release? the commit is > https://github.com/gwtproject/gwt/commit/dd215d81ce29db42b185ffa2f86f6af36076f3be > Its included in 2.8.0-beta1 (see little tag icon + text on

Re: GWT 2.8.0 RC1

MUCH thanks! On 12/03/2015 12:06 PM, Thomas Broyer wrote: AFAICT, it's coming: http://www.gwtproject.org/release-notes.html On Thursday, December 3, 2015 at 5:15:19 PM UTC+1, Michael Joyner wrote:

Re: GWT 2.8.0 RC1

FWIW, small typo: - JsInterop is graduated from eperimental. On Thursday, December 3, 2015 at 2:04:10 PM UTC-8, Michael Joyner wrote: > > MUCH thanks! > > On 12/03/2015 12:06 PM, Thomas Broyer wrote: > > AFAICT, it's coming: http://www.gwtproject.org/release-notes.html > > On Thursday,

Re: Teavm

Thanks for the link Compiling from source code vs. byte code . That was an interesting read. That discussion tool place one year into the implementation of GWT. Two factors seemed to have played a