[
http://jira.codehaus.org/browse/MGWT-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Johannes Dahle updated MGWT-129:
-------------------------------------
Attachment: mgwt-129.patch
A possible solution for the problem. Note that I haven't been able to run the
tests due to a restricted development environment with proxies and local
repositories. But I've tested hosted mode with multiple modules.
> Multi module projects doesn't work properly in HostedMode.
> ----------------------------------------------------------
>
> Key: MGWT-129
> URL: http://jira.codehaus.org/browse/MGWT-129
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Knut Johannes Dahle
> Attachments: mgwt-129.patch
>
>
> I've recently started to upgrade a GWT 1.5.3 based project to the newest
> version. We used gwt-maven from com.totsp.gwt before, but upgraded to Maven
> 2.x GWT Plugin from codehaus for a couple of months ago.
> I got a problem upgrading since the plugin in combination with GWT 1.6+
> doesn't work so well with a multi module setup. I'll try to give you an
> example.
> Given this example configuration:
> <configuration>
> <modules>
> <module>example1.Example1</module>
> <module>example2.Example2</module>
> <module>example3.Example3</module>
> </modules>
> <runTarget>example1.Example1/Example1.html</runTarget>
> </configuration>
> Were every module is an gwt entrypoint. When you run 'mvn gwt:run' hosted
> mode will start up and serve the Example1 module.
> Say you got this button here named "Go to Example2", which links to
> "example2.Example2/Example2.html".
> If you click this button the browser will try to redirect you to Example2,
> but you will get an exception that hostedmode doesn't know about any Example2
> module.
> This is because the plugin only provides com.google.gwt.dev.HostedMode with
> information of one module, based upon runTarget and not all the modules in
> the configuration.
> If you provide com.google.gwt.dev.HostedMode with a list of modules this will
> work perfectly. It works with GWT 1.5.3, but not with GWT 1.6+.
> Ref com.google.gwt.dev.HostedMode commandline help:
> Google Web Toolkit 1.7.1
> HostedMode [-noserver] [-port port-number | "auto"] [-whitelist
> whitelist-string] [-blacklist blacklist-string] [-logLev
> el level] [-gen dir] [-style style] [-ea] [-server servletContainerLauncher]
> [-startupUrl url] [-war dir] [-extra dir] [
> -workDir dir] [-localWorkers count] module[s]
> I think this can be acvieved by rewriting line 308 in
> RunMojo.java(http://fisheye.codehaus.org/browse/mojo/trunk/mojo/gwt-maven-plugin/src/main/java/org/codehaus/mojo/gwt/shell/RunMojo.java?r=HEAD)
> so it gets the whole module list.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
