Hi,
we currently have a jenkins job that checks out the gwt code from github,
applies the patch and build GWT.
FYI, we did not have any issue regarding this patch for more than a year.
It would be awesome to be using an official release of GWT.
Thanks
Le mercredi 8 octobre 2014 20:49:02 UTC+2,
Build GWT from source if you want to play around with it. You need to:
1.) mkdir gwt cd gwt
2.) git clone https://gwt.googlesource.com/gwt trunk
3.) svn checkout http://google-web-toolkit.googlecode.com/svn/tools tools
4.) cd trunk ant dist-dev
This builds GWT without samples and you can then
We are making steady progress towards GWT 2.7. At this point we are not
accepting any new patches, but we still have a list of issues that we would
like to include in the upcoming release. This is no guarantee that all of
them are going to make it but we are trying our best. Also we are holding
On Thursday, October 9, 2014 3:25:37 PM UTC+2, Daniel Kurka wrote:
We are making steady progress towards GWT 2.7. At this point we are not
accepting any new patches, but we still have a list of issues that we would
like to include in the upcoming release. This is no guarantee that all of
Any chance that Patch 9450 https://gwt-review.googlesource.com/#/c/9450/ for
speeding up the intial start time of SDM will make it?
On Thursday, 9 October 2014 15:04:21 UTC+1, Thomas Broyer wrote:
On Thursday, October 9, 2014 3:25:37 PM UTC+2, Daniel Kurka wrote:
We are making steady
Lots of Elemental patches have been merged in the last few days, but we do
still have a short list that would be nice to get included.
https://gwt-review.googlesource.com/#/c/9098/
https://gwt-review.googlesource.com/#/c/9099/
https://gwt-review.googlesource.com/#/c/9095/
The code appears to
I think this is okay as long as it doesn't cause tests to fail. Elemental
is quite separate from everything else so it seems low risk. Daniel?
On Thu, Oct 9, 2014 at 8:57 AM, Leif Åstrand legi...@gmail.com wrote:
Lots of Elemental patches have been merged in the last few days, but we do
still
I think this call is up to the elemental maintainers (manolo thomas), if
it breaks any tests I will roll it back since we need a green build to be
able to branch.
-Daniel
On Thu, Oct 9, 2014 at 6:57 PM, 'Brian Slesinsky' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com
Well, actually there is no official maintainer for elemental, so Ray would
be the most suitable since he introduced elemental to GWT, but as Goktug
said in this thread, he might not have enough time.
What I've tried to do in my patches is to make the existent elemental test
suite run and pass.
On Thursday, October 9, 2014 10:43:38 PM UTC+2, Roberto Lublinerman wrote:
I think we will better exclude the following three patches from the
release 425e0bb 2b2d81c 920ba90
I will either revert them or fix them with a better alternative. Java
RegExp implementation is really rough
+1 for John's patch 9450 https://gwt-review.googlesource.com/#/c/9450/ (
sorry to devolve the thread into +1's )
On 9 October 2014 14:04, Thomas Broyer t.bro...@gmail.com wrote:
On Thursday, October 9, 2014 10:43:38 PM UTC+2, Roberto Lublinerman wrote:
I think we will better exclude the
On Thu, Oct 9, 2014 at 7:04 AM, Thomas Broyer t.bro...@gmail.com wrote:
On Thursday, October 9, 2014 3:25:37 PM UTC+2, Daniel Kurka wrote:
We are making steady progress towards GWT 2.7. At this point we are not
accepting any new patches, but we still have a list of issues that we would
This is a giant change for us and we don't have a simple way to handle that
even with the tooling that we have. Let's discuss this after the release
cut.
On Wed, Oct 8, 2014 at 9:46 PM, Colin Alworth niloc...@gmail.com wrote:
On Wednesday, October 8, 2014 5:16:18 PM UTC-5, Thomas Broyer wrote:
On Wed, Oct 8, 2014 at 3:15 PM, Thomas Broyer t.bro...@gmail.com wrote:
On Wed, Oct 8, 2014 at 7:11 PM, Colin Alworth niloc...@gmail.com wrote:
Not quite. Anything that continues to return user.client.Element can only
be overridden to return user.client.Element or a subclass.
Ha, didn't
I think the other (probably bigger) problem is method overloads that has
Element as the parameter type instead of return type (as that is no such
thing like co-variant parameter types).
That means for whole story to work, every third-party library needs to do
the same that we did in the SDK;
commit d91ce52ae332a414a86016eb67147d732ecba95c
Author: Matthew Dempsky mdemp...@google.com
Date: Mon Sep 2 18:16:48 2013 -0700
Step towards eliminating com.google.gwt.user.client.Element
This commit changes all methods that used to take a user.Element to
instead take a
16 matches
Mail list logo
