[
http://jira.codehaus.org/browse/MGWT-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof updated MGWT-169:
---------------------------------
Attachment: RunMojo.java
Original patch is not fully satisfying as it uses the first module detected as
runModule, that may not be reproductible when scanner is used.
The attached RunMojo.java uses an alternate solution : getRunModule() is not
modified as it expect a single module to be set. When multiple modules are
supported (gwt 2.0+) the sartupUrl is used to retrieve the module and apply
it's rename-to directive
i.e. runTarget=com.myapp.gwt.Module/Module.html
--> module = com.myapp.gwt.Module
--> startupUrl = myRenameTo/Module.html
Please test and let me know if this fixes this issue.
> support devmode for multiple modules
> ------------------------------------
>
> Key: MGWT-169
> URL: http://jira.codehaus.org/browse/MGWT-169
> Project: Maven 2.x GWT Plugin
> Issue Type: Improvement
> Affects Versions: 1.2
> Reporter: Ryan Heaton
> Attachments: RunMojo.java, support-for-multiple-devmode-modules.diff
>
>
> Version 1.2 of the plugin requires a single module to be supplied to devmode.
> While a single module was required to be supplied for hostedmode and
> gwtshell, devmode expects all modules to be supplied. Effectively, this means
> nobody with multiple modules using gwt 2.0+ can use the gwt maven plugin for
> devmode.
> Please apply the attached patch.
--
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
