[
http://jira.codehaus.org/browse/MGWT-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Boll updated MGWT-147:
---------------------------
Attachment: AutoDiscoveryNoEntryPoint.diff
A possible solution is to check for entry points only when modules were
collected using auto-discovery or when ${gwt.compiler.force} is true.
This solution does not include validation of inherited entry points.
> GWT modules with inherited entry point are never compiled
> ---------------------------------------------------------
>
> Key: MGWT-147
> URL: http://jira.codehaus.org/browse/MGWT-147
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Henri Sara
> Attachments: AutoDiscoveryNoEntryPoint.diff
>
>
> The plugin incorrectly considers all modules without an entry point specified
> directly in the module to be secondary modules
> (CompileMojo.compilationRequired() returns false). GWT supports inherited
> entry points, which are often useful e.g. in combination with GWT generators.
> Such modules are never compiled but a message saying they are up-to-date is
> printed. Also the force setting is ignored.
> In gwt-maven-plugin 1.1, modules with inherited entry point are compiled
> correctly.
--
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
