Release notes are here:
http://www.gwtproject.org/release-notes.html#Release_Notes_2_7_0_RC1
--
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
It looks like the gwt-codeserver jar will still exist, but the same classes
will also be in gwt-dev.jar. So it's ugly but should be backward compatible?
- Brian
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group
Yes, merging the jars should be fine as a short-term fix.
Codeserver should be built as a separate library to enforce that there are
no circular dependencies. (We already have one for DevMode -superDevMode
but that should be fixed by splitting out DevMode; it doesn't belong in the
same library as
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
- Make sure sample apps work with DevMode -superdevmode
- I think we're waiting on a patch to CLDR 25
On Wed, Oct 1, 2014 at 12:15 PM, 'Daniel Kurka' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
Hi all,
we just settled on a GWT 2.7 release plan:
- We *code
It's experimental and hidden behind a flag, but it's there.
On Wed, Oct 1, 2014 at 6:20 PM, Cristian Rinaldi csrina...@gmail.com
wrote:
- JsInterop Preview is part of the release?
El miércoles, 1 de octubre de 2014 16:15:26 UTC-3, Daniel Kurka escribió:
Hi all,
we just settled on a GWT
Oops. This particular bug shouldn't be hard to fix.
On Tue, Sep 30, 2014 at 10:50 AM, Brandon Donnelson branflake2...@gmail.com
wrote:
Just a thought, the folks that forget to update Java 1.6 to Java 1.7 in
their project and run SDM (super dev mode) will have issues. A warning
could be
Actually, that particular stack trace should be fixed by this uncommitted
patch:
https://gwt-review.googlesource.com/#/c/9361/
However, I haven't tested it on Java 1.6.
On Tue, Sep 30, 2014 at 11:48 AM, Brian Slesinsky skybr...@google.com
wrote:
Oops. This particular bug shouldn't be hard
This sounds like it might be a deadlock. Could you jstack to get a thread
dump of the running process? It should tell us where it's stuck.
On Tue, Sep 9, 2014 at 8:42 AM, Jens jens.nehlme...@gmail.com wrote:
recentish ones are:
267ad5efd00aae9b0f69eca793891e9fdad28e45 Opts compilePerFile
On Mon, Sep 8, 2014 at 3:00 PM, Jens jens.nehlme...@gmail.com wrote:
And a last question just popped up again: Is there any way to force
embedded Jetty of CodeServer to not print out request logs at DEBUG level?
Kind of annoying when all these progress requests show up between GWT logs.
I'm eager to start using Java 8 too, but I think we should wait until we
have Java 8 committed (behind a flag) before having the discussion about
whether to require it for anything. As we've found with incremental
compile, sometimes we end up changing direction a bit to reach our goal, so
there's
It would make sense in principle but we don't know anyone who wants to
target older browsers without also using permutations.
On Tue, Jul 15, 2014 at 3:55 AM, Jens jens.nehlme...@gmail.com wrote:
I believe Google builds applications that use Elemental and/or JsInterop,
so they don't use
I don't understand the details enough to make an informed recommendation,
but I think introducing a new entry point is a good time to transition to
the standard way (assuming it is standard).
We could add the backward-compatibility flag if needed after some testing
to see what the breakage would
If you click Tutorial and then Documentation the animation is a bit
unfortunate. Because the previous menu closes at the same time that the new
one opens, the new menu expands both up and down so that your cursor ends
up pointing to the middle of the new menu, and then you have to wait until
it
For the direction of an open source project, people who volunteer to do
actual coding are more important than marketing efforts by people who only
want to be users. The intersection of GWT developers and Firefox browser
developers seems to be the empty set, so we have very limited influence.
This
the code server to serve the symbol
map as well, at some special URL?
10 април 2014, четвъртък, 00:16:43 UTC+3, Brian Slesinsky написа:
If you are debugging interactively, using pause on uncaught exceptions
can help. Then you can look at the stack frames in the debugger.
Another workaround
If you are debugging interactively, using pause on uncaught exceptions
can help. Then you can look at the stack frames in the debugger.
Another workaround is to log stack traces to the server and use
StackTraceDeobfuscator. This will also help you in production:
It's true these are disadvantages. There are some compensating advantages
that people are pointing out: the code executes faster, it works with
remote websites where latency is higher, it works with mobile phones, and
so on. But there's no question that losing DevMode (other than IE and
Firefox
In my testing they do sometimes work but it is certainly flaky. I recommend
adding a GWT.debugger() call and recompiling; that should always work,
unless something is really wrong.
- Brian
On Monday, March 3, 2014 12:44:06 PM UTC-8, Ben Hegarty wrote:
Hi,
I was wondering if anyone is seeing
.
On Tuesday, 4 March 2014 18:19:59 UTC, Brian Slesinsky wrote:
In my testing they do sometimes work but it is certainly flaky. I
recommend adding a GWT.debugger() call and recompiling; that should always
work, unless something is really wrong.
- Brian
On Monday, March 3, 2014 12:44:06 PM UTC-8
I'm not sure what the Jetty problems are but they should be fixed. Do we
have a good bug report for them?
(In our setup we see stack traces but Jetty still runs.)
- Brian
On Thu, Feb 27, 2014 at 4:51 PM, joerg.hohwil...@googlemail.com
joerg.hohwil...@googlemail.com wrote:
Hi there,
I can
I believe it's just an idea. In practice, we have lots of GWT generator
code that's not easily migrated.
I'm not familar with APT but if I wanted to learn about it I would probably
start by studying Guice's AutoValue. If they're using JavaWriter then
that's a good endorsement.
- Brian
On Thu,
I'm not sure there's much to discuss. Firefox 27 is already released, and
we do want to move off of Dev Mode sooner or later for other reasons. I
don't feel comfortable asking them to bring back an API that they never
officially supported anyway and it seems unlikely that they'd agree.
Running
Super Dev Mode works and we have many teams that use it. The Chrome
debugger is quite good and I recommend learning it well; anyone working on
web apps will benefit from knowing this tool. For other browsers, adding a
GWT.debugger() call to the Java code and recompiling is an easy way to stop
in
Maybe turn on soft permutations in a sample app, since we do at least test
those manually before a release.
Long-term, I'd like to see us using soft permutations by default, perhaps
to collapse some browser permutations. If it were more commonly used then
we'd likely notice that it's broken
Yes it sounds like a bug. Want to add that to the issue tracker?
I wonder why more people aren't seeing this? Does it only affect soft
permutations?
- Brian
On Thu, Feb 13, 2014 at 11:41 AM, Stephen Haberman step...@exigencecorp.com
wrote:
Hey,
We upgraded to GWT 2.6 last week, and our
I'm not an Eclipse user, but we did upgrade to Jetty 8.1 in 2.6 and its
package changed. If you put the new version of Jetty in your classpath that
will probably fix it.
- Brian
On Thu, Feb 13, 2014 at 6:44 AM, Stephan Beutel stephan.beu...@gmail.comwrote:
I also tried it with the Eclipse
I just ran a bulk edit to change all 2.6 bugs marked fixed not released
to fixed. Thanks for catching that!
(Switching to a different issue tracker is a whole different discussion.)
- Brian
On Wed, Feb 5, 2014 at 11:22 AM, Gilberto Torrezan Filho
gilberto.torre...@gmail.com wrote:
Hi,
I
Mozilla has stopped exporting some C++ symbols that the Firefox plugin
relies on [1]. Therefore it's not possible to support Development Mode in
any new versions of Firefox starting with 27.
As a workaround, I am doing one last release to get the plugin working
again with Firefox 24.2 (and
Perhaps have an occasional meeting day on the mailing list or in G+, sort
of like a Reddit Ask me anything? This might work better with people in
different timezones.
On Mon, Jan 27, 2014 at 11:39 AM, Goktug Gokdogan gok...@google.com wrote:
Just FYI, our gwt-team meetings didn't get enough
Generally I just exclude the super classes from the project; since there
should always a server-side equivalent, the rest of the code should still
compile. You lose syntax checking on the super files, though.
On Wed, Jan 15, 2014 at 12:10 PM, Danilo Reinert danilorein...@gmail.comwrote:
I'm
Sometime in January after people are back from vacation.
On Mon, Dec 30, 2013 at 11:42 AM, Cristiano
cristiano.costant...@gmail.comwrote:
Hello all,
it is many days I don't see info about the release date for GWT 2.6.0...
I see in GWT issues there are 7 issues for milestone 2_6 that are not
This is well-documented and looks like solid work. I think the main issue
will be whether it can be made compatible with modular compilation. So the
best timing will be to land it after modular compilation.
It looks like it should be compatible because the compiler doesn't need to
see how a
I'm not familiar with Windows 8, but I believe you have to run Chrome
outside metro mode to get plugins to work.
http://blog.chromium.org/2012/07/npapi-plug-ins-in-windows-8-metro-mode.html
On Friday, November 29, 2013 10:24:24 AM UTC-8, Joshua Zeidner wrote:
Hi Millie,
I'm experiencing
It's fairly complicated to build because we have to do a C++ compile
against the latest XulRunner SDK on three platforms and assemble the
results. Furthermore, converting a new XulRunner SDK into the format needed
to do the build is a partially manual process. But if you just want to
build on
For GWT 2.6, Super Dev Mode, and the RemoteServiceServlet, you could set
the gwt.codeserver.port Java property.
On Wed, Nov 20, 2013 at 1:35 AM, Jens jens.nehlme...@gmail.com wrote:
The issue comes up when we change a piece of shared code, like a DTO. What
we've found is that if we don't
I suspect the way we're selecting the correct DLL for the Firefox version
is not working somehow. For now, download this version:
https://code.google.com/p/google-web-toolkit/downloads/detail?name=gwt-dev-plugin-1-24-rc.xpi
On Wed, Nov 6, 2013 at 2:17 AM, Thomas Broyer t.bro...@gmail.com
Not a compiler expert, but I wouldn't be surprised since in the AST it will
be represented as a binary tree of JBinaryOperation nodes and the visitors
walk the tree recursively. So balancing the tree should result in a smaller
stack.
- Brian
On Wed, Oct 30, 2013 at 1:10 PM, Julien Dramaix
On Wed, Oct 23, 2013 at 11:59 AM, Jens jens.nehlme...@gmail.com wrote:
Hmm. It's a fair point. On the other hand, you don't *have* to upgrade
right away.
Hehe sure, but its hard to resist Java7, @GwtIncompatible support and
compiler/code splitting bug fixes ;-)
But maybe I misunderstood
I was able to find a virtual machine running Windows 8 and the front page
of www.gwtproject.org seemed to load okay. If you have specifics about what
they saw and how to reproduce it, that would help.
That said, I think GWT would be a poor fit for a company that is mainly
targeting IE8. If
Modular compilation probably won't be ready for GWT 2.6. If it's there at
all, it will be experimental.
On Tuesday, October 22, 2013 6:02:46 AM UTC-7, Thomas Broyer wrote:
On Tuesday, October 22, 2013 2:33:59 PM UTC+2, jesty wrote:
Thanks to all for the answer.
About this features:
*
I expect that by next summer devmode will *only* work in IE and perhaps an
older version of Firefox. Oddly enough, the IE plugin has apparently worked
for years with no complaints. (But the issue is that nobody currently on
the team has ever built it.)
- Brian
On Mon, Oct 21, 2013 at 6:56 AM,
For (1), Super Dev Mode supports multiple GWT apps out of the box. (but you
do have to recompile each GWT application you want to debug, one at a time).
For (2) I don't think we support multiple instances of the same GWT app. I
don't think it's a good idea because you'd be loading the same
Okay, we previously talked about having some kind of deprecation policy and
I'm fine with that; it seems a lot more limited in scope.
I think a reasonable thing to do is to announce that we're dropping a
browser version one release before it happens, so we should decide now
about what we're going
On Tue, Oct 8, 2013 at 12:15 PM, Jens jens.nehlme...@gmail.com wrote:
[...] since in practice we won't consider ourselves bound to them.
Why not?
Because we'll either we'll forget about that page due to turnover or
something new will happen and priorities will change. Put it this way: how
, and decisions are made in public so
anyone can bug you when you forget. That's a different situation than
before.
Le 8 oct. 2013 22:43, Brian Slesinsky skybr...@google.com a écrit :
On Tue, Oct 8, 2013 at 12:15 PM, Jens jens.nehlme...@gmail.com wrote:
[...] since in practice we won't consider
I haven't tried it, but it says here that Gradle has support for publishing
to Maven:
http://www.gradle.org/docs/current/userguide/publishing_maven.html
On Sat, Sep 28, 2013 at 10:49 PM, Cristiano Costantini
cristiano.costant...@gmail.com wrote:
Hello,
What do you think of having gradle (or
September 25, 2013
-
Hangout on air today
-
Matt shared the GWT 2.6 release plan
(dochttps://docs.google.com/a/google.com/document/d/1ZdMwcTjc4rkWg6nntCY1BDB1xI2PHPwaCnTYw-9uAKE/edit
)
-
feature-complete November 4th. Release on December 2.
-
Bhaskar: which
On Thu, Sep 26, 2013 at 10:26 AM, Jens jens.nehlme...@gmail.com wrote:
In terms of Gradle vs Buck models, is there any possibility of writing
a tool that takes a Buck build file and produces Gradle files? That would
seem like a good option in lieu of waiting for Buck support in IntelliJ and
I skimmed the Gradle manual and it looks pretty decent. While the syntax
and terminology is different, it looks like the concepts map back to stuff
I'm already comfortable with.
It has tasks which are basically build rules which are configured via
Groovy (instead of Python macros). The tool
As a stop-gap measure, can you clean up and check in your IDEA module(s)?
- Brian
On Wed, Sep 25, 2013 at 9:20 AM, Ray Cromwell cromwell...@google.comwrote:
The biggest problem with being a GWT contributor today is that it is hard,
very hard, to set up an environment to develop. If you look
about doing
this as well, but changing hosted.html keeps it consistent across the board.
On Tuesday, September 24, 2013 6:50:07 PM UTC-5, Brian Slesinsky wrote:
Hi,
Wow, thanks for tracking this down! Could you send a patch that just
modifies the source (not worrying about the autogenerated
September 18, 2013
Talking about Q4 goals:
* Separate compilation: more people to help John? How to divide the work?
Java / JavaScript integration: Ray says he's going to be working on this
for Q4, along with Closure compiler integration.
* SuperDevMode: fast compile cycles is most important.
Here are some notes for our last few meetings. I'm sure a comparison
between our notes and the YouTube video [1] would show I missed a few
things. :-)
[1] https://www.youtube.com/watch?v=hIgR7-3ZAMc
September 4, 2013
Brian: meeting with someone working on Chrome devtools to get up to speed.
Hi, my guess is that it's just an oversight; at Google we have our own
build stystem so we don't use the ant scripts all that often. If you want
to dive in, I'd be interested in what you find.
- Brian
On Sat, Aug 31, 2013 at 2:33 PM, Daniel Trebbien dtrebb...@gmail.comwrote:
Hi,
I am trying
Thanks for looking into how to improve Java stack traces. I agree that we
could do a better job. However, there are some problems with your approach:
First of all, we can't guarantee that we will accept this change. That
doesn't seem very fair to whoever might be donating money.
I would like to
Thanks for looking into how to improve Java stack traces. I agree that we
could do a better job. However, there are some problems with your approach:
First of all, we can't guarantee that we will accept this change. That
doesn't seem very fair to whoever might be donating money.
I would like to
Interesting. I like the idea of replacing class parameters with something
else. I'm not sure we need to sweep the implementation under the rug.
Particularly in fancier scenarios, it might be easier to work with it
explicitly.
Suppose we have:
/** Encapsulates a GWT create call. */
interface
It seems like a nice project, but integrating it into GWT will slow down
both the GWT developers and the SpiffyUI developers a lot. There would have
to be some pretty compelling reasons to do that. Otherwise, better to let
them keep doing what they're doing, and let them ask for specific changes
I did do some profiling and at the time it looked like a good 40% was spent
in the JDT. It will depend on the app though; I'm not satisfied I
understand the performance.
I've built some infrastructure for collecting better performance metrics
inside Google, but at the moment I've put that aside
2. IDE support: IDE can trigger codegen (esp. for debugging)
My experience with this has been pretty poor, and running GWT with -gen is
at least as useful.
Also, Super Dev Mode gives you access to all the generated code. You can
either use the browser's debugger with SourceMaps turned
for the
long run.
On Fri, Aug 9, 2013 at 1:24 PM, Brian Slesinsky skyb...@google.comwrote:
Hi, I've published a document [1] with my thoughts on some of the
GWT.create() proposals. This doesn't cover everything we've discussed but I
think it's a start. If you're on this mailing list you should be able
for a Google team
I would be nice to hear how this was done on such large projects as Google
has. I try with out application (170k LOC of client code / GWT-RPC, etc.)
and it took 2x-3x more time then DevMode.
On Thursday, August 8, 2013 11:04:04 PM UTC+2, Brian Slesinsky wrote:
I haven't been
Hi, I've published a document [1] with my thoughts on some of the
GWT.create() proposals. This doesn't cover everything we've discussed but I
think it's a start. If you're on this mailing list you should be able to
comment.
- Brian
[1]
I've published that doc here:
https://docs.google.com/document/d/1MDqiBEMl7dylYliAceLBBxGFAlSvkQB9b-kSlnKmZBk/edit?disco=AGXNBZg#heading=h.gks1bp7hz61l
To clarify, I'm not myself working on any GWT.create() enhancements, but I
thought it was worth documenting my concerns in greater detail
It might be nice to be able to say that anything defined in a .d.ts can be
imported into GWT. This will make it easier to work with JavaScript
programmers since they don't have to write any Java code. So perhaps it's
worth making sure that generating the Java interfaces from .d.ts files will
work?
I haven't been sending out emails for our meetings. Let's catch up:
August 7th:
- John got a hello world app running using separate compilation. We
talked a bit about how it might get pulled back into GWT.
- Brian: Firefox architecture changes may break the Development Mode plugin
by the end of
some kind of standard plugin extension.
On Thu, Aug 8, 2013 at 9:08 AM, Brian Slesinsky skybr...@google.comwrote:
It might be nice to be able to say that anything defined in a .d.ts can
be imported into GWT. This will make it easier to work with JavaScript
programmers since they don't have
Our plan is to make Super Dev Mode compile faster. Plan B is to use an
extended release of Firefox for a while. (I believe Firefox 24 is the next
one.)
Despite appearances, I'm not actually a C++ programmer and I'm not plugged
into the Firefox community enough to know how realistic it is that
I just pushed out an update for Firefox 23 yesterday. Firefox 22 should
have been unaffected (I didn't rebuild the Windows binary for 22) but
perhaps something went wrong.
For comparison, the previous release is here:
https://dl.google.com/dl/gwt/plugins/firefox/1.22/gwt-dev-plugin.xpi
But
shouldn't be used with Firefox 22.
Nonetheless, I was able to reproduce the bug using Firefox 22. It doesn't
happen with Firefox 23.
On Tuesday, August 6, 2013 11:11:35 AM UTC-7, Brian Slesinsky wrote:
I just pushed out an update for Firefox 23 yesterday. Firefox 22 should
have been
: master
Gerrit-Owner: Brian Slesinsky skybr...@google.com
Gerrit-Reviewer: John Stalcup stal...@google.com
Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org
Gerrit-Reviewer: Matthew Dempsky mdemp...@google.com
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received
Brian Slesinsky has posted comments on this change.
Change subject: Super Dev Mode: deemphasize unused Java lines in
codeserver's UI
..
Patch Set 1:
(7 comments)
File
: master
Gerrit-Owner: Brian Slesinsky skybr...@google.com
Gerrit-Reviewer: Brian Slesinsky skybr...@google.com
Gerrit-Reviewer: John Stalcup stal...@google.com
Gerrit-Reviewer: Leeroy Jenkins jenk...@gwtproject.org
Gerrit-Reviewer: Matthew Dempsky mdemp...@google.com
--
http://groups.google.com/group
Brian Slesinsky has submitted this change and it was merged.
Change subject: Super Dev Mode: deemphasize unused Java lines in
codeserver's UI
..
Super Dev Mode: deemphasize unused Java lines in codeserver's UI
Modified
Hi, in the interest of increased transparency, I'm going to start posting
notes from GWT team meetings at Google. I'm not sure if we'll keep this up
but we'll see how it goes. (My apologies in advance for any errors.)
June 26, 2013
- Discussed goals for the next quarter. Of interest to the
Brian Slesinsky has posted comments on this change.
Change subject: Optimize initializing fields at the top scope.
..
Patch Set 3:
(2 comments)
File dev/core/src/com
Brian Slesinsky has uploaded a new change for review.
https://gwt-review.googlesource.com/3600
Change subject: Super Dev Mode: deemphasize unused Java lines in
codeserver's UI
..
Super Dev Mode: deemphasize unused Java
Brian Slesinsky has posted comments on this change.
Change subject: Fix support for Document.{get,set}ScrollLeft() in RTL for
safari and ie9.
..
Patch Set 4: Verified+1 Code-Review+2
Looks like all issues have been
Brian Slesinsky has submitted this change and it was merged.
Change subject: Fix support for Document.{get,set}ScrollLeft() in RTL for
safari and ie9.
..
Fix support for Document.{get,set}ScrollLeft() in RTL for safari
Update: as far as I know, nobody worked on this today. But on the bright
side, nothing had to be rolled back.
(I worked on getting the Firefox plugin ready for Firefox 22. It should be
out on time.)
On Thu, Jun 20, 2013 at 3:32 PM, Matthew Dempsky mdemp...@google.comwrote:
As a ~24h later
Brian Slesinsky has posted comments on this change.
Change subject: Adds isStandalone to ImageResource so Image can used an
UnclippedState.
..
Patch Set 8:
Had to roll this back again due to projects that implement
Brian Slesinsky has posted comments on this change.
Change subject: Add hasClassName method in com.google.gwt.dom.client.Element
..
Patch Set 7:
As mentioned above, there's a conflict with Sencha which bit us when we
tried
Brian Slesinsky has posted comments on this change.
Change subject: Adds an accessor to original throwable from
SerializableThrowable.
..
Patch Set 1: Code-Review+1
(1 comment)
Seems basically okay
Brian Slesinsky has posted comments on this change.
Change subject: Adds an accessor to original throwable from
SerializableThrowable.
..
Patch Set 2: Code-Review+2
(1 comment
, 2013 at 10:20 PM, Brian Slesinsky skybr...@google.comwrote:
I agree; this seems like a workaround for one application that picked the
wrong datatype. Maybe we should warn about BigDecimal being slow somewhere?
If someone wants to do some performance tests of GWT-RPC serialization,
publishing
Another possibility would be to develop a nicer GWT RichTextArea as a
separate open source project. There's no reason it has to be in core GWT
right away and you'll be able to work faster that way. With real-world
usage, you'll probably learn a few things that will make it better quality
if we do
Brian Slesinsky has posted comments on this change.
Change subject: Adding a DOM clear method to RootPanel
..
Patch Set 6:
(1 comment)
I still don't think it's necessary but I'm okay with a helper method if
it's very
I agree; this seems like a workaround for one application that picked the
wrong datatype. Maybe we should warn about BigDecimal being slow somewhere?
If someone wants to do some performance tests of GWT-RPC serialization,
publishing the results would be useful to the community.
My recommendation
Brian Slesinsky has posted comments on this change.
Change subject: Adding a DOM clear method to RootPanel
..
Patch Set 6:
Admittedly it's a judgment call. I'm somewhat biased in favor of shorter
names and somewhat against
Brian Slesinsky has posted comments on this change.
Change subject: Use JSON.parse() instead of eval() to deserialize rpc
callback payload
..
Patch Set 11:
Sounds like we need more tests. Serialization code generally does
Brian Slesinsky has posted comments on this change.
Change subject: Adding a DOM clear method to RootPanel
..
Patch Set 6: Code-Review+2
This is a pretty minor change, breakage is unlikely, and I don't think it
matters too
Lazy parsing can be a performance win, but it also complicates the API in
the case of a parse error. Have you thought about how to report errors when
they happen later?
It might less confusing to solve this using a separate LazyBigDecimal
class. People can declare fields of this type in their
Brian Slesinsky has posted comments on this change.
Change subject: Fix non-final field initializers running before the super
cstr.
..
Patch Set 9:
Regarding git procedure, I've already rolled back on google/pu and we
Brian Slesinsky has posted comments on this change.
Change subject: Fix non-final field initializers running before the super
cstr.
..
Patch Set 9:
Oops, that wasn't very clear. Let me try again:
If think you're going
Brian Slesinsky has posted comments on this change.
Change subject: Fix non-final field initializers running before the super
cstr.
..
Patch Set 9:
Hi, we had a performance regression reported to us so we rolled this CL
+mdempsky
Hi, I think you're going to have more trouble than most because you're
using Windows and that's not so common for GWT development. The code to
automatically add the Change-Id line is specific to Unix but you can do it
manually by editing the changelist yourself. To fix your most recent
Brian Slesinsky has posted comments on this change.
Change subject: Remove unused, package-private FastStringMap.
..
Patch Set 1: Code-Review+2
Not used in Google code either.
--
To view, visit https://gwt
Brian Slesinsky has posted comments on this change.
Change subject: The job of defineSeed is to mark the existence of a class
and associate its castMap with the class's various constructors.
..
Patch Set 2:
(1 comment
On Wed, Jun 5, 2013 at 7:46 PM, Stephen Haberman
step...@exigencecorp.comwrote:
I don't have a good idea about what could break
I believe nothing would break--it's that final fields that were
previously not going over the wire would now go over the wire.
It's also possible that the newly
1 - 100 of 395 matches
Mail list logo
