i'm using google plugin for eclipse 3.5 (galileo) with GWT 2.0.0 (and
app engine 1.2.8).

when i compile my GWT modules, i set the additional compiler arguments
to "-war war/foo." the behavior is as expected: the compiler creates
directories for each module under "war/foo." i get the following
directories when i compile only:

war/foo/mymodule1
war/foo/mymodule2
and so on...

when i run a web application, the compiler goes back to using the
default directory ("war") to create directories for each module. under
Run Configurations, there is no option to add additional compiler
arguments under the GWT tab. i get the following directories when i
run:

/war/mymodule1
/war/mymodule2
and so on...

clicking the refresh button in the hosted browser window seems to have
the same effect as running the web app: it uses directories in the
default location. even though the actual web page points to to the
"war/foo" location, the app reflects the new changes immediately. the
web page includes the following script:

<script src="/foo/mymodule1/mymodule1.nocache.js"></script>

i checked the actual output files to see which ones were modified and,
sure enough, war/foo/mymodule1/mymodule1.nocache.js was NOT touched.
war/mymodule1/mymodule1.nocache.js was modified. again: the web app
seems to reflect the changes, even though the script src points to the
non-default directory. i'm assuming that the client-side code is just
running in the same VM as the server in hosted browser mode.

i'm hoping that the option to specify additional GWT compiler
arguments can be added to the GWT tab under Run Configurations, just
as it is available under the GWT compile dialog.

--

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.


Reply via email to