[
http://jira.codehaus.org/browse/MGWT-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177617#action_177617
]
nicolas de loof commented on MGWT-82:
-------------------------------------
As discussed on MGWT-76, m2eclipse can be used to avoid packaging of dependent
modules and use them as project references. This could make GWT productivity
far better, but MAY require some tweaks on the gwt:run classpath to handle well
project references when passed by m2eclipse as artifacts (getFile() then
returns the related project outputDirectory in replacement for the
localRepository artifact file)
Note that the plugin MUST ensure that the related improvement does not allow
bad design by referencing in a GWT webapp project other projects source code
as GWT inherits wihtout having those modules well defined as GWT library :
* have java sources included as resources in the artifacts
* have a dedicated gwt.xml module file with inheritence set to required modules.
> Better support for m2eclipse integration
> ----------------------------------------
>
> Key: MGWT-82
> URL: http://jira.codehaus.org/browse/MGWT-82
> Project: Maven 2.x GWT Plugin
> Issue Type: Improvement
> Affects Versions: 2.0
> Reporter: nicolas de loof
>
> Using m2eclipse, dependencies can be resolved as project references and then
> a source code modification in the dependent project should be detected and
> applied by the Hosted Browser with a simple refresh
--
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
