Ah, brilliant. That did it.
Here's a follow up. I have my project set up Maven-style (using Maven
3.0.3). What can I do to my configuration such that running "mvn
clean install" will build a functioning WAR each time? My only idea
is to add an antrun plugin directive to delete the src/main/webapp/
*nocache.js files that are generated, but maybe there's something I
should be doing in the configuration. Configuration is ...
<!-- GWT Maven Plugin -->
<plugin> <groupId>org.codehaus.mojo</
groupId>
<artifactId>gwt-maven-plugin</artifactId>
<version>$
{gwtVersion}</version> <executions>
<execution>
<goals> <goal>clean</goal>
<goal>compile</goal>
<goal>test</goal> </goals>
</execution>
</executions>
<!-- Plugin configuration. There are many available options, see gwt-
maven-plugin documentation at codehaus.org
-->
<configuration>
<runTarget>index.html</runTarget>
<hostedWebapp>${webappDirectory}</hostedWebapp>
<i18nMessagesBundle>com.myco.clearing.product.client.Messages</
i18nMessagesBundle> </configuration>
</plugin>
Thanks, - Dave
On Nov 28, 9:39 am, Thomas Broyer <[email protected]> wrote:
> Did you run the GWT compiler before packaging your WAR?
>
> If you did, then delete the *.nocache.js generated by the DevMode (Run As
> -> Web Application) and re-GWT-compile your project.
>
> The thing is: when running DevMode, if there's no *.nocache.js or it seems
> to be stale, a new one is generated, containing only the minimum code
> required to run in DevMode. You need to GWT-compile just before you package
> your WAR, make sure the *.nocache.js is a "full" one (and of course that
> the rest of the compiled code, the *.cache.* files, are up-to-date too).
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
