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
<webappDirectory>../ninja/src/main/java/assets/gwt</webappDirectory>
(aka gwt.war parameter) so that gwt compiled its js sources into the
assets folder of our server.
With the old devmode this worked nicely (as I said - the project was
not touched for five years...).
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 workaround? Like telling SuperDevMode where to put its
nocache files to? If not I have to integrate that into the build of
our java dev server I guess...
Thanks!
Raphael
On Fri, Apr 22, 2016 at 12:47 PM, Jens <jens.nehlmeier@gmail.com> wrote:
> 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 Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscribe@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment