[
http://jira.codehaus.org/browse/MGWT-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221561#action_221561
]
Brian Reilly commented on MGWT-183:
-----------------------------------
This has been working for me, but I only just realized it's because I'm using
1.3-SNAPSHOT rather than 1.2. It looks like there is now logic to find entry
points from inherited modules, so CompileMojo.compilationRequired won't
immediately return false for these cases.
> Cannot compile a module that inherits a module with entry points
> ----------------------------------------------------------------
>
> Key: MGWT-183
> URL: http://jira.codehaus.org/browse/MGWT-183
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Jon Bass
>
> CompileMojo.compilationRequired returns false if a module has no entry
> points. But a module may inherit from another module that has entry points,
> in which case it is incorrectly ignored.
> It is useful to create sub-modules with different settings for production vs
> dev etc.
> The workaround I am using is to define my entry points in the sub modules and
> remove from the parent. Not a bad workaround but not intuitive, and error
> prone!
--
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
