Instead of using the regular Google Eclipse Plugin launchers, you could use a regular Eclipse launcher and pass the arguments there. For a more detailed explanation, look at this post:
http://blog.salvadordiaz.fr/2009/04/29/keep-your-source-tree-clean-gwt/ The last bullet point in the section "Eclipse project configuration" Hope that helps, Salvador On May 5, 8:43 am, denis <[email protected]> wrote: > I have the same issue. > With the regular compiler, I can avoid stack overflow error thanks to > -Xmx512m -Xms128m -Xss8M in the VM arguments box. > > But, with GWT compiler, I have not found a way to set these arguments, > and the compiler is stopped with the stack overflow error. > Using GWT compiler is automated for App Engine deployment. > > What shall I do? > > Denis > > On 30 avr, 18:06, Vitali Lovich <[email protected]> wrote: > > > On Thu, Apr 30, 2009 at 10:25 AM, [email protected] < > > > [email protected]> wrote: > > > > I'm waiting for it too and its starting to take time just for two > > > options... > > > Why does deploying force compilation (which fails so badly) ? > > > Because that's what deployment is? Maybe I'm not understanding your > > question. Hosted mode (which runs the Java code in a JVM) is just for > > debugging. For deployment, you compile the Java code into actual > > Javascript. > > > > BTW what does it change to use GWT trunk ? > > > From what I could tell, not much. But there could be more unknown bugs & > > whatnot. However, it should compile - according to the Google developers, > > they have other internal teams working against trunk. > > > > I'm using it and I still have the issue... (and I can't deploy and > > > oophm doesn't have a compile button yet, fortunately i can compile > > > with ant) > > > So what's the issue? What do you mean you can't deploy? You just said you > > can compile with ant. OOPHM should get the compile button eventually - I > > never found a particular need to use it. Just run your ant script. > > > > On 23 avr, 15:59, Miguel Méndez <[email protected]> wrote: > > > > We've updated the compile UI to allow you to tweak the -Xss and -Xmx > > > > settings. It will be part of the upcoming point release of the plugin. > > > > In the meantime, the compile button in hosted mode is one work around. > > > You > > > > can also compile a version of the GWT trunk and have the plugin use that > > > SDK > > > > for the project. > > > > > On Thu, Apr 23, 2009 at 3:51 AM, mihai007 <[email protected]> wrote: > > > > > > oh well add me to the list. this should have priority as it turns the > > > > > use of plugin useless if I can't compile.... > > > > > any workarounds? > > > > > > On 8 Abr, 16:11, Brian <[email protected]> wrote: > > > > > > Just installed the Google plugin for Eclipse, and hit the Compile > > > > > > button on my project. It gave me astackoverflowerror. > > > > > > Prior to using the plugin, I'd compile by hitting the Compile button > > > > > > in the hosted mode browser. In the Run/Debug Eclipse configuration, > > > I > > > > > > have -Xss4k & -Xmx256M > > > > > > Compiles worked fine with those flags and the Compile button from > > > > > > hosted mode. > > > > > > > How do I set the Xss flag for use by the Compile button in the > > > eclipse > > > > > > toolbar? I tried putting it in the Advanced section, but this just > > > > > > informed me it wasn't an appropriate gwt compiler option. > > > > > > > This isn't stopping me from doing anything, as I can still compile > > > > > > from hosted mode, just curious how to set it up. I checked the > > > plugin > > > > > > faq, but couldn't find anything there. > > > > > -- > > > > Miguel > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
