[ 
http://jira.codehaus.org/browse/MGWT-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174571#action_174571
 ] 

nicolas de loof commented on MGWT-60:
-------------------------------------

The Async code generation is a lightweight process, and the inclusion pattern 
can be used to avoid uncessary class check. 

A timestamp-check would apply after
- scanning for "to-be-generated classes" using pattern
- check for RemoteInterface to be implemented by candidate interfaces

We can know which class have to be generated, and then could use a timestamp 
check, only after 90% of the work is allready done.

> Create a staleFlag configuration on pom.xml
> -------------------------------------------
>
>                 Key: MGWT-60
>                 URL: http://jira.codehaus.org/browse/MGWT-60
>             Project: Maven 2.x GWT Plugin
>          Issue Type: Improvement
>    Affects Versions: 1.1
>            Reporter: Felipe desiderati
>            Priority: Minor
>
> There is a configuration (parameter) available on XML Beans Maven Plugin, 
> named staleFile. It is responsible for verifying if the xsd has changed, and 
> if yes, it informs to XML Beans Plugin to create the new java source.
> I think it will be great if the generateAsync goal has a configuration like 
> this, avoiding the Async interface creation every time you call "compile", 
> since the generateAsync is bounded to generate-sources phase, that is before 
> the compile phase. 
> I know that if we don´t declare the generateAsync goal on our POM, under the 
> maven-gwt-plugin, we still can call it directly from command line using goal 
> gwt:generateAsync. But I think it´s more intuitive to just call compile.

-- 
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


Reply via email to