Ah! - there is another gwt plugin :) Good to know! My missing link was
that I did not know that SuperDevMode creates a special nocache.js
file. Once I knew that it was simple to fix.
I'll try your plugin asap...
Thanks!
Raphael
On Fri, Apr 22, 2016 at 5:56 PM, Thomas Broyer
Assuming the Mojo plugin and gwt:run-codeserver; you'll need to set the
launcherDir
property:
https://gwt-maven-plugin.github.io/gwt-maven-plugin/run-codeserver-mojo.html#launcherDir
If using gwt:run, then AFAICT it'd be
hostedWebapp:
Hmm. I just tried some options of the maven plugin but that did not
work. But it's not important anyway. I integrated build step into our
java server that copies over the nocache.js files of the gwt project
into its assets folder. That works for both the superdevmode and the
regular ones (when
> SuperDevMode does not seem to respect gwt.war when compiling its
> superdevmode.nocache.js. And that is the problem. The special
> superdevmode.nocache.js gets created in the target folder of the
> original gwt project. Our Java server knows nothing about it...
>
> Is there a good
That did the trick. Now it's working... Thanks Jens! I did not know
that there is a special SuperDevMode nocache.js file needed.
Now things are a bit clearer. We used
../ninja/src/main/java/assets/gwt
(aka gwt.war parameter) so that gwt compiled its js sources into the
assets folder of our
First start SDM, then deploy your war to your external server. SDM
generates a special *.nocache.js file that enables automatic recompilation.
You have to make sure that this special version is deployed.
-- J.
--
You received this message because you are subscribed to the Google Groups "GWT
Hi,
I just ran into an interesting problem while upgrading a very old GWT
app to GWT 2.8.0-beta1 and its SuperDevMode (using the codehaus maven
plugin).
Our setup is basically that we got two projects: A GWT project, and a
Java Server that acts as restful json backend.
If I compile stuff via
