When you use Maven and Eclipse, you import a Maven project (ou create one
from within Eclipse), and the GPE detects the use of the gwt-maven-plugin
and auto-configures itself, using the GWT dependencies from your Maven
project rather than a GWT SDK (so you can really use any GWT version
that's
Awesome. We are switching to 2.7 in our next release.
Prashant,
www.pratilipi.com
On Thu Nov 20 2014 at 10:26:21 PM Tom Legrand thomas.legr...@axellience.com
wrote:
Great news! We're going to switch to 2.7 in our next sprint
Great to see it compiles even faster in the super dev mode
On
Hi, I have the same problem. what did you do?
Thanks.
El miércoles, 19 de mayo de 2010 19:49:46 UTC+2, lmolinero escribió:
Hi, I've run into a problem after migrating form GWT 1.7 to GWT 2.0.3
one of my rpc is failling in 2.0.3 and throwing this:
java.lang.AssertionError: Not enough
Yes.. my doubts are based on the IBM jvm
have you find any difference among the Oracle JVM and IBM JVM...
when compile GWT?
And is Jetty a good Server for try application before to deploy on iSeries?
or otherwise.. do you use WebSphere for iSeries directly when you develop?
Il giorno
On the first view on your stack trace, I've seen, that the sources for the
backend is missing . Put the sources of each lib/fw in your buildpath, it
should change the stack trace, at least
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
I guess it is largely related to the fact that it's Java and most people in
web-development come from the Javascript side of things and for them Java
is much more verbose than Javascript (this will change when GWT supports
the Java 8 syntax).
Dart has basically the same problem. People are
On Friday, November 21, 2014 11:33:48 AM UTC+1, Thomas Broyer wrote:
When you use Maven and Eclipse, you import a Maven project (ou create
one from within Eclipse), and the GPE detects the use of the
gwt-maven-plugin and auto-configures itself, using the GWT dependencies
from your Maven
Awesome! Thanks so much to all the guys working on this. You are legends.
Quick question - has anyone had any problems with deploying to appengine
using the maven-gae-plugin? I tried a couple of times with 2.7rc1 and when
I tried to load the deployed version it seemed to be looking for the dev
On Friday, November 21, 2014 6:54:29 PM UTC+1, Phineas Gage wrote:
- You still want separate GWT and app engine SDKs installed in Eclipse,
even though you've also got them in your local maven repository.
I can't tell for App Engine, but why would you want a GWT SDK?
--
You received this
Quick question - has anyone had any problems with deploying to appengine
using the maven-gae-plugin? I tried a couple of times with 2.7rc1 and when
I tried to load the deployed version it seemed to be looking for the dev
mode server.
Maybe you accidentally deployed the module.nocache.js
With the advent of 2.7 I am determined to get going with SuperDevMode.
However, once my development environment (Eclipse) is all set to run the
code server when I try to load my application using SuperDevMode I get the
following error. This actually happens whether I compile with debug mode
I see, I am on my own with this issue...
Nevertheless, I post my proceedings here. Maybe it helps someone someday...
Well: There must be some side effect between the SDM dialog box (div) which
shows Choose a module to recompile and my library test code.
My library test code also is a DialogBox,
Can that be an option ? So that the user knows what happens consciously, in
order to optimize the runtime. I admit, that this would not simplify the
jscompiler base code, but would provide the user with another powerful
optimization...
Just an idea...
Thanks
Arnaud
Le vendredi 21 novembre
The one of the problems is the boxing makes the support of method
overloading, var args, etc. more complicated and much slower in JsInterop.
Making it optional is not going to help with those.
I think with the experiment we will have a very good data on the impact of
this change, after that we can
It could be conditioned on jsinterop being switched on or not, in
general though, more and more compiler switch modes I think encourage
lazy/bad code practices in the ecosystem.
Better would be a lint/checked mode that throws hard errors in
your app when you do something that violates the
It could be conditioned on jsinterop being switched on or not, in
general though, more and more compiler switch modes I think encourage
lazy/bad code practices in the ecosystem.
Conditioned on jsinterop would really be bad, since all js wrapper libs
will soon be based on jsinterop which
16 matches
Mail list logo
