[mojo-dev] [jira] (MGWT-186) Generic Interface is not generated correctly

Thu, 21 Jun 2012 16:45:24 -0700

 
Will Jordan edited a comment on Bug MGWT-186

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

svn checkout http://svn.codehaus.org/mojo/trunk/mojo/gwt-maven-plugin/src/it/mgwt-186
cd mgwt-186
sed -i -e 's/@pom.version@/2.4.0/' -e 's/@gwt.version@/2.4.0/' pom.xml



2. Run generateAsync and check generated interface




mvn gwt:generateAsync -q && grep -i getEnabledSubjects target/generated-sources/gwt/org/codehaus/mojo/gwt/test/client/SubjectServiceAsync.java






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





sed -i 's/List<Subject>/List<String>/' src/main/java/org/codehaus/mojo/gwt/test/client/SubjectDao.java






4. Run generateAsync and check generated interface





mvn gwt:generateAsync -q && grep getEnabledSubjects target/generated-sources/gwt/org/codehaus/mojo/gwt/test/client/SubjectServiceAsync.java






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




mvn clean -q






6. Run generateAsync and check generated interface




mvn gwt:generateAsync -q && grep -i getEnabledSubjects target/generated-sources/gwt/org/codehaus/mojo/gwt/test/client/SubjectServiceAsync.java






output (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.
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
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to