|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MGWT-186) Generic Interface is n... Will Jordan (JIRA)
- [mojo-dev] [jira] (MGWT-186) Generic Interface... Will Jordan (JIRA)
- [mojo-dev] [jira] (MGWT-186) Generic Interface... Tim Fleming (JIRA)
- [mojo-dev] [jira] (MGWT-186) Generic Interface... Marnix Klooster (JIRA)
- [mojo-dev] [jira] (MGWT-186) Generic Interface... Thomas Broyer (JIRA)

I'm still seeing this bug, and have consistently reproduced the issue within the integration test mentioned. This should be enough to go by to identify and fix the problem.
Steps below (commands for a *nix system listed):
1. Checkout integration test (and replace placeholders in pom.xml):
2. Run generateAsync and check generated interface
[output]
> void getEnabledSubjects( AsyncCallback<java.util.List<org.codehaus.mojo.gwt.test.client.Subject>> callback );
3. Edit the DAO to return List<String> instead of List<Subject>:
4. Run generateAsync and check generated interface (note the signature hasn't changed, when it should have)
> void getEnabledSubjects( AsyncCallback<java.util.List<org.codehaus.mojo.gwt.test.client.Subject>> callback );
5. Clean Maven build
6. Run generateAsync and check generated interface (note it finally changes)
> void getEnabledSubjects( AsyncCallback<java.util.List<java.lang.String>> callback );
The workaround is to clean the build's generated sources when seeing this error.