Anything that can serve files from the file-system can be used with SDM: just pass "-launcherDir path/to/some/directory" to the CodeServer and it will output a *.nocache.js in there that triggers a recompile on page load.
On Monday, February 2, 2015 at 2:30:40 PM UTC+1, Ali Akhtar wrote:
-- On Monday, February 2, 2015 at 2:30:40 PM UTC+1, Ali Akhtar wrote:
I'd like to use GWT with SDM in a project that doesn't use servlets, instead its using the vert.x framework, with IntelliJ.Currently, I have two run configurations in IntelliJ.The first one starts the vert.x web framework which listens on port 80, and on http://localhost , it sends my host.html file.The second run config is a standard GWT SDM run configuration from IntelliJ. That one starts the gwt code server on localhost:1978My host.html file contains this tag during development:<script type="text/javascript" src="http://127.0.0.1:9876/MyModule/MyModule.nocache.js "></script> and during production, it switches to:<script type="text/javascript" src="MyModule/MyModule.nocache.js"></script> When I first visit http://localhost , the module auto re-compiles. However on subsequent refreshes, it doesn't recompile, and I have to use the old bookmarklet method to trigger a recompile manually. This also seems to do a full recompile rather than incremental.Is there a way to trigger incremental recompiles automatically on reload, even though I'm not using the standard servlet based project layout?Does GWT check the source files to see if they've changed when it triggers a recompile on reload, or does it check compiler output (e.g in target/classes)?
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 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 http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment