[
http://jira.codehaus.org/browse/MGWT-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-201.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.3
module inheritence is allready fixed in 1.3
> Sources directories in inherited modules are ignored
> ----------------------------------------------------
>
> Key: MGWT-201
> URL: http://jira.codehaus.org/browse/MGWT-201
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Shay Rojansky
> Priority: Minor
> Fix For: 1.3
>
> Attachments: testcase.tar.bz2
>
>
> When one gwt inherits from another, the parent's source directories aren't
> taken into account when compiling the child.
> This kind of two-module project configuration is common when wanting to have
> a testing "light" project module which only generates one Firefox/English
> permutation (rather than compiling all permutations).
> When trying to compile the child project (mvn gwt:compile
> -Dgwt.module=myGroupId.ApplicationLight in the attached testcase) you always
> get "myGroupId.ApplicationLight is up to date. GWT compilation skipped".
> It seems like a matter of org/codehaus/mojo/gwt/GwtModule.java, and making
> getSources(), getSuperSources() include the inherited modules' respective
> list. I'd do it if the approach is confirmed by someone how actually knows
> something about the plugin and GWT :)
> Shay
--
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
