[
http://jira.codehaus.org/browse/MGWT-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191210#action_191210
]
David J. M. Karlsen commented on MGWT-117:
------------------------------------------
Hmm - if I've understood you right this reminds me of the same problem I had
about a year ago.
Have you tried building sourceartifacs of the dependant artifacts and adding
them as a dependency in the gwt module with the <type>source</type>.
Even if that works your solution is probably preferable as the one I used would
mean a lot of more I/O to package source archives.
Just thought it was worth mentioning.
> Add support for multiple source directories to make modular GWT projects
> easier
> -------------------------------------------------------------------------------
>
> Key: MGWT-117
> URL: http://jira.codehaus.org/browse/MGWT-117
> Project: Maven 2.x GWT Plugin
> Issue Type: New Feature
> Affects Versions: 1.1
> Reporter: Matt Raible
> Attachments: multiple_source_directories.patch
>
>
> In my experience, I've found that if I modularize a GWT application[1], I
> have to "mvn install" my "core" application and restart hosted mode every
> time I make changes.
> I'd like to see support for multiple source directories like the
> jetty-maven-plugin has:
> http://docs.codehaus.org/display/JETTY/Multiple+WebApp+Source+Directory
> I believe this could be very useful for modularizing GWT applications.
> [1] http://raibledesigns.com/rd/entry/modularizing_gwt_applications_with_gwt
--
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
