Hi Thomas,
Thanks for your answer.
Here is a stackoverflow post (december 2011) which points on the freezing
problem I was encoutering at this time
(http://stackoverflow.com/questions/8564872/maven-project-builder-is-invoked-every-time-i-change-a-source-file-gwt).
The proposed answer was to
On Monday, November 10, 2014 9:31:53 AM UTC+1, Francois ANDRE wrote:
Hi Thomas,
Thanks for your answer.
Here is a stackoverflow post (december 2011) which points on the freezing
problem I was encoutering at this time (
Then I can't understand how that could happen, sorry… (unless isScript()
erroneously evaluated to 'true' maybe?)
That code has changed slightly in 2.7 (for nearly the reverse behavior as
you're seeing: issue 8548
https://code.google.com/p/google-web-toolkit/issues/detail?id=8548) so
maybe you
Are you sure there isn't any other deferred binding property that could
generate the second permutation?
The xsiframe linker (used by default in 2.7) should generate
a compilation-mappings.txt file that can tell you which properties led to
each permutation.
On Monday, November 10, 2014 1:11:00
Greetings,
I am running a large application in SDM in Eclipse and I am getting a
java.lang.OutOfMemoryError: Java heap space error:
*Out of memory; to increase the amount of memory, use the -Xmx flag at
startup (java -Xmx128M ...)*
Is there a way to increase the memory?
Thank you!
Oleg
--
Open run configurations. In the arguments tab you can increase the VM:s
memory allocation with:
-XX:MaxPermSize=512m -Xmx1024m in the VM arguments box.
On Monday, November 10, 2014 12:40:53 PM UTC+1, Oleg Cohen wrote:
Greetings,
I am running a large application in SDM in Eclipse and I am
I did try to upgrade to 2.7-rc1 but got some compiler errors, I also
upgraded the gwt maven plugin to 2.7-rc1. Then I read that SDM was the
default so I added the flag so that DM would be used...but still got the
compiler errors. Could be that I have some 3rd party GWT code that isn't
compatible
On Monday, November 10, 2014 3:40:32 PM UTC+1, dhoffer wrote:
I read on http://mojo.codehaus.org/gwt-maven-plugin/whats_new.html that
2.7-rc1 was updated to use 2.6.1?? That seems wrong to me.
Ah, forgot to update the maven site…
--
You received this message because you are subscribed
Go to project-Run Configurations-Select Web Application and delete the
file.Now run your project as web application.My problem got solved.
Also check arguments tab to confirm the path .For com.Myproject.gwt.xml
mention com.Myproject in arguments.Sometimes it also gives error because of
GWT
I can't see any other deferred binding property, but I'm not an expert here.
If I replace the user.User inherits with core.Core and useragent.UserAgent,
then I do get the expected two permutations, not four. So something in
there is forcing it to be more, but I don't know what that is, nor
Piyush,
It rarely makes sense to respond to several-year-old posts, and the
original poster said that the problem was resolved.
On Monday, November 10, 2014 12:17:06 PM UTC-8, Piyush wrote:
Go to project-Run Configurations-Select Web Application and delete the
file.Now run your project as
Hello,
Tests generators in GWT 2.6.0.
public class rttiGenerator extends Generator {
@Override
public String generate(TreeLogger logger, GeneratorContext context,
String typeName) throws UnableToCompleteException {
JClassType classType;
try {
classType =
Put the generator outside of your source path so that the gwt compiler does
not try to compile it to javascript.
-- J.
--
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
W dniu 11.11.2014 o 02:03, Jens pisze:
Put the generator outside of your source path so that the gwt compiler does
not try to compile it to javascript.
You were right.
Now I changed the path and the generator is working but there is another
problem
public class rttiGenerator extends
Hi Daniel,
It's good to have GWT super dev mode in many aspects. But there are still
some issues that made me decide to go back to the 2.6.1, some of them are
critical:
1- First of all, I actually have a problem with my huge project, and the
browser says:
Uncaught
Hi all, I just updated a project using GWT 2.6.1 with version 2.7.0.
Everything seems to works client side (after adding some dummy property on
the gwt.xml), the problem is server side.
I noticed that my WLS 12.1.1 stopped working after one deploy, so I started
digging and I've found that the
On Monday, November 10, 2014 10:45:37 AM UTC+1, luca.masini wrote:
Hi all, I just updated a project using GWT 2.6.1 with version 2.7.0.
Everything seems to works client side (after adding some dummy property on
the gwt.xml), the problem is server side.
I noticed that my WLS 12.1.1
I added that dependency only because I use RegExp and I cannot use JRE's
Matcher.
I don't use GWT-RCP, I make REST calls.
But it's a good idea, I'll dump the PermGen content to see what is inside.
L.
Il giorno lunedì 10 novembre 2014 12:17:14 UTC+1, Thomas Broyer ha scritto:
On Monday,
On Monday, November 10, 2014 12:40:50 PM UTC+1, luca.masini wrote:
I added that dependency only because I use RegExp and I cannot use JRE's
Matcher.
I don't use GWT-RCP, I make REST calls.
This is strange because regexp hasn't changed:
I'm glad you solved it.
For future references, in general it is good idea to keep the strict
enabled - though some libraries that are not in your control might cause
compilation problems that you cannot fix without changing the lib.
On Sun, Nov 9, 2014 at 11:16 PM, Erik Kuefler ekuef...@gmail.com
Sorry, I didn't mean that there is a change in behaviour in RegExp, only
that I used gwt-servlet because I needed to use that on client and on
server side.
Il giorno lunedì 10 novembre 2014 15:39:30 UTC+1, Thomas Broyer ha scritto:
On Monday, November 10, 2014 12:40:50 PM UTC+1,
I'm glad you solved it.
For future references, in general it is good idea to keep the strict
enabled - though some libraries that are not in your control might cause
compilation problems that you cannot fix without changing the lib.
IMHO GWT 3.0 should turn on -strict by default and
Well, you have a difference of behavior wrt PermGen, right? ;-)
--
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
23 matches
Mail list logo
