It would indeed work (most of the time I believe), but then you need to
make sure to force the GWT compiler to compile your code before deploying,
because it's really easy to get false positives in the staleness check (if
the superdevmode stub *.nocache.js modification time is more recent than
I added in a local maven profile an extra property file to instruct sprint
boot where check the static resources.
spring.resources.static-locations=${gwtBasePathLocation},classpath:/META-INF/resources/,classpath:/resources/,classpath:/static/,classpath:/public/
On Wed, 6 Mar 2019 at 11:13 Bryan
I was able to set the launcherDir to server/target/classes/static and that
seems to make it work the way I was expecting.
On Tuesday, 5 March 2019 13:55:54 UTC-5, Bryan Bende wrote:
>
> Hello,
>
> I have a multi-module Maven project setup similar to the multi-module
> archetype, but created befo
Hello,
I have a multi-module Maven project setup similar to the multi-module
archetype, but created before I knew about that, using GWT 2.8.2 and the
gwt-maven-plugin 1.0-rc-9.
shared - Contains DTOs with JS interop annotations, packaged as gwt-lib
client - GWT code, depends on shared as gwt-li
