GWT 2.8 RC1

Goktug Gokdogan

unread,

Oct 28, 2015, 4:46:54 AM10/28/15

to google-web-toolkit-contributors

Hey guys.

We are planning to make the release cut by next Monday to start testing sooner. Hopefully by the time we will complete most of the critical pieces for JsInterop.

Also FYI, JDT has a huge memory problem with Java8 so doing a final release without a fix may make the release less useful for a lot of people. Let's hope that gets fixed soon.

Paul Robinson

unread,

Oct 28, 2015, 8:53:17 AM10/28/15

to google-web-tool...@googlegroups.com

Speaking for myself, a GWT 2.8.0 release that works, but uses too much memory compiling code, to be followed by GWT 2.8.1 with the memory fix, is better than waiting for an unknown amount of time until JDT is fixed.

--
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/CAN%3DyUA1Se5eNCNjwS5F8c-wzc7BYqd0rWY%2Bq--Yg9cP7353UnA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Seamus McMorrow

unread,

Oct 28, 2015, 9:57:37 AM10/28/15

to GWT Contributors

To try to speed up the fix, maybe if people voted for the issue, it may help.

I just cast my vote to get it fixed.

On Wednesday, 28 October 2015 12:53:17 UTC, Paul Robinson wrote:

Speaking for myself, a GWT 2.8.0 release that works, but uses too much memory compiling code, to be followed by GWT 2.8.1 with the memory fix, is better than waiting for an unknown amount of time until JDT is fixed.

On Wed, Oct 28, 2015 at 8:46 AM, 'Goktug Gokdogan' via GWT Contributors <google-web-toolkit-contri...@googlegroups.com> wrote:

Hey guys.

We are planning to make the release cut by next Monday to start testing sooner. Hopefully by the time we will complete most of the critical pieces for JsInterop.

Also FYI, JDT has a huge memory problem with Java8 so doing a final release without a fix may make the release less useful for a lot of people. Let's hope that gets fixed soon.

--
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+unsubscribe@googlegroups.com.

Colin Alworth

unread,

Oct 28, 2015, 10:14:58 AM10/28/15

to GWT Contributors

Paul, do keep in mind that the latest in git (and the 2.8.0-SNAPSHOT in maven) is fairly stable. Some projects (for example, everything that Google makes) live off of trunk, and many projects upgrade to a snapshot, test that things are sane, and then 'pin' that build internally to keep running with it until they decide to update again.

On Wed, Oct 28, 2015 at 8:57 AM Seamus McMorrow <seamusm...@gmail.com> wrote:

To try to speed up the fix, maybe if people voted for the issue, it may help.
I just cast my vote to get it fixed.

On Wednesday, 28 October 2015 12:53:17 UTC, Paul Robinson wrote:

Speaking for myself, a GWT 2.8.0 release that works, but uses too much memory compiling code, to be followed by GWT 2.8.1 with the memory fix, is better than waiting for an unknown amount of time until JDT is fixed.

On Wed, Oct 28, 2015 at 8:46 AM, 'Goktug Gokdogan' via GWT Contributors <google-web-tool...@googlegroups.com> wrote:

Hey guys.

We are planning to make the release cut by next Monday to start testing sooner. Hopefully by the time we will complete most of the critical pieces for JsInterop.

Also FYI, JDT has a huge memory problem with Java8 so doing a final release without a fix may make the release less useful for a lot of people. Let's hope that gets fixed soon.

--
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/CAN%3DyUA1Se5eNCNjwS5F8c-wzc7BYqd0rWY%2Bq--Yg9cP7353UnA%40mail.gmail.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-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/09999856-c756-4493-936d-41be54f8d33d%40googlegroups.com.

Paul Robinson

unread,

Oct 28, 2015, 10:21:17 AM10/28/15

to google-web-tool...@googlegroups.com

Yes, I know. The thing is, there's always a level of paranoia about GWT's impending doom and apparent lack of activity shown in the gwt users group, and a release coming at an unknown time helps to fuel that paranoia.

Having said that, I've voted for the bug :)

To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CADcXZMyM%3DZut%3DHky4hcWunWZL0WWmH%2B0xNDY5KrshM8k4F48wg%40mail.gmail.com.

Jens

unread,

Oct 28, 2015, 11:01:00 AM10/28/15

to GWT Contributors

The thing is, there's always a level of paranoia about GWT's impending doom and apparent lack of activity shown in the gwt users group, and a release coming at an unknown time helps to fuel that paranoia.

Maybe we should post everything in https://groups.google.com/a/gwtproject.org/forum/#!forum/gwt-reviews also to the gwt users group to defeat that paranoia once and for all. You would never run short on activity then ;-)

That being said I think its fine to have RC builds even with that memory issue to get people test the RC. But the final release of 2.8 should have a fixed JDT to make sure everyone can use it. I am pretty sure there are quite some people who simply can not increase their heap by 50-100%.

-- J.

Thomas Broyer

unread,

Oct 28, 2015, 11:25:47 AM10/28/15

to GWT Contributors

Will those people switch to Java 8 at the same time they upgrade to GWT 2.8? I doubt it.

If (as I understand it) the leak only happens when using "-sourceLevel 8", then I'm fine with a 2.8.0 without waiting for the fix (but a big bold warning in the release notes), and a 2.8.1 as soon as the fix is available.

Jens

unread,

Oct 28, 2015, 1:25:49 PM10/28/15

to GWT Contributors

Will those people switch to Java 8 at the same time they upgrade to GWT 2.8? I doubt it.
If (as I understand it) the leak only happens when using "-sourceLevel 8", then I'm fine with a 2.8.0 without waiting for the fix (but a big bold warning in the release notes), and a 2.8.1 as soon as the fix is available.

Well if thats the case then fine. Also GWT snapshot users haven't complained yet so maybe its generally not that a big issue unless you actually have a big GWT project. The issue talks about 35000 classes which are quite a few. But if you have a big GWT project you probably have enough RAM anyways.

-- J.

Goktug Gokdogan

unread,

Oct 28, 2015, 2:28:51 PM10/28/15

to google-web-toolkit-contributors

People will not be able to use '-sourceLevel 7" once the JRE patches for java 8 starts getting submitted.

So the idea was to default to -sourceLevel 8. This is ok because what version GWT used to compile source doesn't effect their code so most people wouldn't have noticed it (if there wasn't a memory issue).

--
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/9b8e5adf-6a64-4e4f-b44c-d649f6d5fb58%40googlegroups.com.

Slava Pankov

unread,

Nov 7, 2015, 4:43:54 AM11/7/15

to GWT Contributors

Is there any chance to include this fix into 2.8 RC1 https://gwt-review.googlesource.com/#/c/12990/

This fix is tiny and simple, but prevents a lot of annoyance in my project.

On Wednesday, October 28, 2015 at 11:28:51 AM UTC-7, Goktug Gokdogan wrote:

On Wed, Oct 28, 2015 at 8:25 AM, Thomas Broyer <t.br...@gmail.com> wrote:

On Wednesday, October 28, 2015 at 4:01:00 PM UTC+1, Jens wrote:

The thing is, there's always a level of paranoia about GWT's impending doom and apparent lack of activity shown in the gwt users group, and a release coming at an unknown time helps to fuel that paranoia.

Maybe we should post everything in https://groups.google.com/a/gwtproject.org/forum/#!forum/gwt-reviews also to the gwt users group to defeat that paranoia once and for all. You would never run short on activity then ;-)

That being said I think its fine to have RC builds even with that memory issue to get people test the RC. But the final release of 2.8 should have a fixed JDT to make sure everyone can use it. I am pretty sure there are quite some people who simply can not increase their heap by 50-100%.

Will those people switch to Java 8 at the same time they upgrade to GWT 2.8? I doubt it.
If (as I understand it) the leak only happens when using "-sourceLevel 8", then I'm fine with a 2.8.0 without waiting for the fix (but a big bold warning in the release notes), and a 2.8.1 as soon as the fix is available.

People will not be able to use '-sourceLevel 7" once the JRE patches for java 8 starts getting submitted.
So the idea was to default to -sourceLevel 8. This is ok because what version GWT used to compile source doesn't effect their code so most people wouldn't have noticed it (if there wasn't a memory issue).

--
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+unsubscribe@googlegroups.com.

Reply all

Reply to author

Forward