GWT 2.7.0 is here

[Daniel Kurka]

Today we are excited to announce the GWT 2.7.0 release.  Thanks to everyone who contributed to this release, especially our non-Google open source contributors.

One major feature of this release is a new super fast compilation path in Super Dev mode that replaces the old dev mode.

For a run-down of all changes since GWT 2.6.1, read the release notes.

The release is available for download here or on maven central.

If you find any issues with this release, please file a bug in our issue tracker.

Daniel,

on behalf of the GWT team at Google

[Juan Pablo Gardella]

Awesome!!

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-tool...@googlegroups.com.
To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[Luca Morettoni]

Well done Daniel (and all the GWT developer community)!! Proud to have
met you in Firenze!

--
Luca Morettoni <luca(AT)morettoni.net> | http://www.morettoni.net
http://it.linkedin.com/in/morettoni/ | http://twitter.com/morettoni
Google+ profile: https://www.google.com/+LucaMorettoni
Member of GDG Perugia: http://perugia.gtugs.org

[Luca]

Waiting for Maven Central......

[Jens]

Waiting for Maven Central......

https://repo1.maven.org/maven2/com/google/gwt/gwt-user/2.7.0/

Maven search website just doesn't reveal it yet.

-- J. 

[Christoph Henrici]

Great!!! Excited to get to try JSInterop , albeit experimential

[Luca]

Now it's there, when I tried Maven build failed.

Thank you, now I want to test all my projects :)

[Saiki Tanabe]

Thank you! Wov it really compiles fast after the first compilation. This really makes a difference in development. In small change Sketchboard.io used to take 5 - 6 seconds to compile and now it takes little bit over a 1 second, I am impressed.

Saiki

--

http://sketchboard.io - Make a complex problem simple together. Sketch.

[apanizo]

Fantástico!

[Tom Legrand]

Great news! We're going to switch to 2.7 in our next sprint

Great to see it compiles even faster in the super dev mode

[Ali Akhtar]

I've just updated to 2.7.0 through maven, and each time I run it, the browser gets stuck on the 'Compiling [ModuleName]' screen. In chrome's console, I see this error:

 Uncaught ReferenceError: moduleName is not defined :9876/ModuleName/ModuleName.recompile.nocache.js:349 

I've tried stopping and restarting a few times, no luck.

Any ideas?

[Prashant]

Awesome. We are switching to 2.7 in our next release.

Prashant,

www.pratilipi.com

[Drew Spencer]

Awesome! Thanks so much to all the guys working on this. You are legends.

Quick question - has anyone had any problems with deploying to appengine using the maven-gae-plugin? I tried a couple of times with 2.7rc1 and when I tried to load the deployed version it seemed to be looking for the dev mode server.

Am I missing a parameter or something like that?

Cheers

Drew

[Jens]

Quick question - has anyone had any problems with deploying to appengine using the maven-gae-plugin? I tried a couple of times with 2.7rc1 and when I tried to load the deployed version it seemed to be looking for the dev mode server.

Maybe you accidentally deployed the <module>.nocache.js file produced by DevMode/SDM ? 

-- J.

[Peter Ondruška]

Thanks but still no update on Eclipse update site (as mentioned in http://www.gwtproject.org/download.html). And fix the wording on the same page: "The Google Plugin for Eclipse provides IDE support for the GWT and App Engine web projects, and includes a lightweight version of GWT Designer". GWT Designed has gone.

On Thursday, 20 November 2014 11:59:06 UTC+1, Daniel Kurka wrote:

[Drew Spencer]

I'm really not sure. I just run mvn gae:deploy which runs my tests, compiles if needed and then completes the interaction with the server.

If I deploy using 2.6.1 it's fine, it's just a bit annoying as I have to do a total clean time I switch between 2.7 and 2.6.1.

Meh

[Drew Spencer]

Hmm, in my <appDir> I have a project.nocache.js and a project.devmode.js. Not sure If I can exclude them though as they are generated at compile time aren't they? 

Surely I can't be the only one with this problem?

Drew

[Pavel Kakolin]

Looks like new GWT requires much more memory to compile applications. Eg. after switching to 2.7, almost every build of our application on buildagents with 32 bit java8 with -Xmx1440m fails with OOM (native).

On Thursday, November 20, 2014 11:59:06 AM UTC+1, Daniel Kurka wrote:

[jaga]

Yes. I noticed it needs double the memory. Also the -port parameter does not seem to work in Eclipse. Finally, and most importantly, I could not get the source maps to work. They don't appear in chrome dev tools. I had it all working in 2.6.1.

[Drew Spencer]

I find the source maps works sometimes, but sometimes not. I've heard other say the same as well. Haven't been able to reproduce it with any level of consistency either so who knows what's causing it!

[James Wendel]

I wanted to say thank you to the entire GWT team for this release.  Incremental compiling for SDM has made it where we can use it at my company and it's seems great in my initial testing on it.  Being able to reload a page instantly when there are no changes (or only a few seconds to reload when there are changes) is awesome.  I really appreciate the work the GWT team has done.

Thanks,

-James

[Zied Hamdi]

Hi Daniel,

These are good news, the bad news is the fact that we won't be able to use eclipse with all its developement shortcutted features (source navigation, breakpoint and bookmark management, tasks, etc...). The solution is an eclipse plugin that will read the sourcemap and display/communicate with the browser to dispatch debug events. The good news is that there's already on project doing this, but the bémol is that the sourcemap spec is leaking some vital information: see this bug for example https://groups.google.com/forum/#!topic/sdbg/Ku3WWrdtKis

Do you think GWT can allocate some of the energy they were spending in the browser plugin to fix this kind of issues?

I just want to underline that GWT's success was: develop in Java and run in the browser. Now there's a big piece of the "develop in java" that was cut off: debugging and source navigation while running. So it's the heart of the spirit of GWT that has been touched with the superDevMode

Unless the strategy is to migrate projects towards dart and drop GWT out, I think this feature is vital for the success of GWT to keep going

On Thursday, November 20, 2014 11:59:06 AM UTC+1, Daniel Kurka wrote:

[malcolm.davis]

I still see only 2.6.0 SDK as the latest version from the https://dl.google.com/eclipse/plugin/4.4 update site in eclipse, and it is now mid January.  Is this going to be updated?  Or is there a problem at my end?  And if the latter, what is the fix?  Thanks.

[Thomas Broyer]

Distribution as an Eclipse plugin is managed by the Google Plugin for Eclipse team, ask them on their group or report on their issue tracker (sorry, don't have the links at the moment).

If you want the latest and greatest, download the zip file and configure it in Eclipse.
…or move to a build tool with managed dependencies (Ivy, Gradle, Maven, etc.) that'll download jars from Maven Central.

[Davis, Malcolm]

Thanks!

--
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/YVKZe2xpQ-Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.

To post to this group, send email to google-we...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

This message (including any attachments) may contain confidential, proprietary, privileged and/or private information. The information is intended to be for the use of the individual or entity designated above. If you are not the intended recipient of this message, please notify the sender immediately, and delete the message and any attachments. Any disclosure, reproduction, distribution or other use of this message or any attachments by an individual or entity other than the intended recipient is prohibited.

[Dave Dumaresq]

Why isn't this available from the Eclipse update site (luna)? For that matter I can't find 2.6.1 there either.

Dave

[Thomas Broyer]

On Thursday, January 22, 2015 at 9:26:55 PM UTC+1, Dave Dumaresq wrote:

Why isn't this available from the Eclipse update site (luna)? For that matter I can't find 2.6.1 there either.

https://groups.google.com/d/topic/google-web-toolkit/tzlin8mX7EU 

[Ali Akhtar]

There appears to be a bug in autobean deserialization in 2.7.0 : https://groups.google.com/forum/#!topic/google-web-toolkit/RzsjqX2gGd4

[showlong]

I tried to use GWT 2.7 SDM with Tomcat server. From Eclipse, I launched our app launcher file used to work with GWT 2.6 Dev mode, and so now with GWT2.7 it becomes SDM by default.
The initial compilation is OK and code server starts fine and our app web server (using GWT RPC) starts fine. But when I tried to load from Chrome, the page is empty and the console said cannot load module nocache.js file. I searched the issue and found a old post with workaround to point the moudule nocache.js file to code server instead of the web server: https://code.google.com/p/google-web-toolkit/issues/detail?id=8886

But then I need to use "Dev on" bookmarklet to recompile it and I need to force to set one permutation properties on the gwt.xml file.
Does anyone have this issue or know how to fix it so that I can fully use GWT 2.7 SDM without these workarounds to refresh browser to recompile the code?

[Jens]

I tried to use GWT 2.7 SDM with Tomcat server. From Eclipse, I launched our app launcher file used to work with GWT 2.6 Dev mode, and so now with GWT2.7 it becomes SDM by default.
The initial compilation is OK and code server starts fine and our app web server (using GWT RPC) starts fine. But when I tried to load from Chrome, the page is empty and the console said cannot load module nocache.js file. I searched the issue and found a old post with workaround to point the moudule nocache.js file to code server instead of the web server: https://code.google.com/p/google-web-toolkit/issues/detail?id=8886

When you start DevMode -war /path/to/war/ then GWT 2.7 will generate a <module>.nocache.js file in the specified war folder. However it does not override any existing <module>nocache.js file. So the best thing you can do is to delete your old /path/to/war/<module> folder so that you start with a fresh one generated by GWT 2.7. After SDM has started you can deploy the war and recompile on reload should work.

The above also means that if you build a production version of your app you should first clean that folder again so you do not accidentally deploy a generated <module>.nocache.js file into production that was actually meant to be used with SDM only.

-- J.

[showlong]

On Tuesday, February 17, 2015 at 3:54:35 PM UTC-8, Jens wrote:

When you start DevMode -war /path/to/war/ then GWT 2.7 will generate a <module>.nocache.js file in the specified war folder. However it does not override any existing <module>nocache.js file. So the best thing you can do is to delete your old /path/to/war/<module> folder so that you start with a fresh one generated by GWT 2.7. After SDM has started you can deploy the war and recompile on reload should work.

The above also means that if you build a production version of your app you should first clean that folder again so you do not accidentally deploy a generated <module>.nocache.js file into production that was actually meant to be used with SDM only.

-- J.

Thanks for your info. I clean the war/client dir and then launch SDM but still the launch page http://127.0.0.1:8888/module.html still cannot load client/module.nocache.js file although the module.nocache.js file is really under war/client/module.nocache.js. This is Tomcat server, does SDM create other server than Jetty different?
I did a test to manually rename the module.nocache.js to module-nocache.js file and upate module.htmi to load client/module-nocache.js file, it works. How come?

[Jens]

Thanks for your info. I clean the war/client dir and then launch SDM but still the launch page http://127.0.0.1:8888/module.html still cannot load client/module.nocache.js file although the module.nocache.js file is really under war/client/module.nocache.js. This is Tomcat server, does SDM create other server than Jetty different?

If you use Tomcat then you launch DevMode -noserver -war <exploded war folder> which tells GWT to not start the Jetty server provided by GWT. Instead GWT assumes that you deploy <exploded war folder> yourself using whatever server you like.

DevMode -noserver -war <exploded war folder> is the same as CodeServer -launcherDir <exploded war folder> . Both just start the SDM code server and don't care about deploying your server side code.

 

I did a test to manually rename the module.nocache.js to module-nocache.js file and upate module.htmi to load client/module-nocache.js file, it works. How come?

 No idea. Most likely there is something strange with your setup.

 

-- J.

[showlong]

If you use Tomcat then you launch DevMode -noserver -war <exploded war folder> which tells GWT to not start the Jetty server provided by GWT. Instead GWT assumes that you deploy <exploded war folder> yourself using whatever server you like.

DevMode -noserver -war <exploded war folder> is the same as CodeServer -launcherDir <exploded war folder> . Both just start the SDM code server and don't care about deploying your server side code.

 

I do  DevMode -server <TomcatLauncher>. The Tomcat server services GWT RPC. Does that make any difference?

[showlong]

I did a test to manually rename the module.nocache.js to module-nocache.js file and upate module.htmi to load client/module-nocache.js file, it works. How come?

 No idea. Most likely there is something strange with your setup.

 

-- J.

I found the issue is our Tomcat server is looking for moudule.nocache.js.zip file which is not auto generated by the codeserver. This recompile-reqester embedded module.nocache.js missed a gz version.

[Jiyuan Zheng]

when will eclipse version of SDK be released? 

[Raj]

hi ...

this is raj i have some problem to the extension of  GWT plug in chrome i already install that extension  GWT Developer Plugin 1.0.11357 but when i run the GWT program  it will gives the message like 

Development Mode requires the GWT Developer Plugin

By downloading, you agree to the Terms of Service and Privacy Policy.

Download the GWT Developer Plugin
For Chrome

plugins for other systems

For help or troubleshooting, ask questions in the discussion group.

what i do help me thanks in advance

[Jens]

The plugin does not work anymore in new versions of Chrome. Use SuperDevMode instead which does not require a browser plugin or install an older browser again.

-- J.

[rakesh pabbathi]

Hi Daniel 

how to i convert my application which is in 2.3 version to 2.7 ? plz provide me some steps to convert the version to 2.7.

[Ed]

| how to i convert my application which is in 2.3 version to 2.7 ? plz provide me some steps to convert the version to 2.7.

As far as I know: there is no migration "guide". 

Just switch to 2.7 and start resolving the compiler errors. It will probably cost you more time in this forum then solving the compiler errors. There aren't soo many for your switch...

If you want to go in to theorie preparation: see the release notes.

Op dinsdag 21 april 2015 15:36:07 UTC+2 schreef rakesh pabbathi:

[lukaslokf...@gmail.com]

great tool. but why do you stop support for linux? is there a way to develop with GWT under linux???

[Michael Joyner]

On 05/12/2015 03:36 PM, lukaslokf...@gmail.com wrote:
> great tool. but why do you stop support for linux? is there a way to
> develop with GWT under linux???

Huh?

I for one only develop using Linux ...

[Alex Sanz]

Hi, it's awesome.

On september I will migrate for 2.5.1 to 2.7.0 but i wonder if do you have a scheduler for the next stable release? for go to the next on september?

Thanks a lot for your awesome work.

Alex Sanz

[DC]

Thumbs up!!!

[John Malpas]

Hello,

I'm repsonsible for @ 50 GWT web apps. I develop
on Windows 7 on a command line, and the apps run
on a commercial Linux server.
Last month (July 2015) I switched from 2.6 to 2.7.
I small thing I noticed right away was that the deliverable file
sizes for 2.7 were uniformly slightly bigger, between 2 and 5%.
But the problem I'm having with 2.7 is when I put out
a newer version of a web app that has already been
loaded into a users' browser.

On the server, the update times for all relevant files (.html, .css,
.js etc.) are set to one week. So if there is a new version of a
web app, users will typically get it within a week. For users who
ask for the latest version right away, I would tell them to
force refresh the browser page.For 2.6 and earlier, this worked reliably
on all browsers I tested (IE Firefox and Chrome on Windows, Firefox
and Chrome on Mac, Chrome on Android). With 2.7, it works sometimes,
but there have been several occasions where I asked the user to
refresh to get the latest version, they did, and they ended up with a dead page.
In other words, the GWT javascript page of the page did not load at all.
Faced with that, I have to tell users to delete their browsing history, and
try again (-- I never had to resort to that extreme step before 2.7).

Faced with that, I decided to go back to 2.6 today, and the problem completely
went away. I asked the same users who ended up with dead pages from the 2.7
version to refresh again to the just published 2.6 version, and the app worked
right away, no problem.

[Thomas Broyer]

2.7 shipped with a bug regarding the mtime of the nocache.js file. Does it work better if you "touch" the file before you deploy it?

[mseele]

When will GWT 2.7.1 be released? We cannot use 2.7.0 cause of the "nocache.js"-bug but whould like to upgrade from 2.6.1...

Am Donnerstag, 20. November 2014 11:59:06 UTC+1 schrieb Daniel Kurka:

[wade...@gmail.com]

I have installed GPE with GWT 2.7 into Eclipse Luna 4.4. Everything works fine.
However, for some reason I have to downgrade JDK from 1.7 to 1.6. After downgrading, the GWT plugin doesn't work anymore.
Does anyone know if GWT 2.7 supports JDK 1.6?

[David Dumaresq]

it sounds like you may have an older version of the gwt-servlet.jar or gwt-user.jar somewhere in your classpath. check your server lib or web-inf/lib. 

dave

---

Education is not the filling of a pail, but the lighting of a fire.

William Butler Yeats

--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.

[Thomas Broyer]

GWT 2.7 works with Java 6, but IIRC the GPE (either Google Plugin for Eclipse or GWT Plugin for Eclipse) requires Java 7; i.e. you need to launch Eclipse with a JRE 7, but then you should be able to pick a JDK 6 for your project and it should work (AFAICT) 

[wade...@gmail.com]

Thanks Thomas. I have tried your solution. I installed the GPE with Java 7 first. Then I selected jre 1.6 in the build path. However, I got an JVM Launcher error "Main class is not found in com.google.appengine.tools.enhancer.Enhance". Looks like this enhancer does not support java 1.6. I disabled this in the eclipse. But it still has problem. Do you know how to solve this issue?