Sounds like a hasle to require a VM... unless that VM would include
everything to get started.
Just setting up eclipse to be inline with the coding guidelines in GWT and
setting up all the libraries etc are really painful and you need to follow
the steps very carefully (and hopefully no
I'm seeing what looks like a regression in my project. I get the following
error when running GWT compilation from Gradle after upping the version.
The error doesn't seem very helpful except that it's possibly related to
code generation and UiBinder:
Compiling module com.MyModule
https://gwt-review.googlesource.com/9810
On Sun, Oct 19, 2014 at 12:47 AM, Julien Dramaix julien.dram...@gmail.com
wrote:
I will work on that tomorrow
On Oct 18, 2014 8:10 PM, 'Daniel Kurka' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com wrote:
Hi all,
apparently
Does adding inherit to c.g.gwt.uibinder.UiBinder fix the issue?
We broke many cyclic dependencies around c.g.gwt.user.User. In this
process, I dropped many unneeded dependencies to User from smaller modules.
As most developers directly depend on User that doesn't have any affect.
However if they
Doesn't seem to help. I did already have a dependency on User. Here's the
full list of inherits from my gwtxml:
inherits name='com.google.gwt.user.User'/
inherits name='com.google.gwt.uibinder.UiBinder'/
inherits name=com.google.gwt.logging.Logging/
inherits
I don't have any other ideas. If you can provide us a simpler repro case,
it would be very helpful.
On Sun, Oct 19, 2014 at 3:11 PM, Erik Kuefler ekuef...@gmail.com wrote:
Doesn't seem to help. I did already have a dependency on User. Here's the
full list of inherits from my gwtxml:
inherits
Hi,
I'm trying out GWT 2.7.0-beta1, and am seeing kind of odd recompile
times. (Our app is ~70k LOC, and the main/only generators are GWT-RPC
and UiBinder.)
The first compile take 40s. Then, only changing a single char in
a .java file, the first recompile takes 20s. Then each next one takes
...and, right now, I can't even get the 3s time to kick in again.
Ah ha...seems to be something with the PersistentUnitCache.
When the recompile is 10-20s every time, I see output of:
Wrote 4944 units to persistent cache
Wrote 1 units to persistent cache
(reload)
Wrote 4944
John detected that behavior in the persistent unit cache and has a fix for
it.
On Oct 19, 2014 7:16 PM, Stephen Haberman stephen.haber...@gmail.com
wrote:
...and, right now, I can't even get the 3s time to kick in again.
Ah ha...seems to be something with the PersistentUnitCache.
When the
The time it takes to compile depends not only on how many files are
modified but also how big is the invalidation caused by the modification.
Depending what gets invalidated it might require running more generators or
(re) compiling many more types.
Also the first few compiles are also warming up
depends on how many files are modified [+ invalidations]
Yeah, sorry, I should have mentioned I've only been changing one file,
just adding/removing a character in a string.
John detected that behavior in the persistent unit cache and has a
fix for it.
Great! I'll try it out when it hits
11 matches
Mail list logo
