|
||||||||
|
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-334) Add support for SuperDev... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Olivier Lamy (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Olivier Lamy (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Thomas Broyer (JIRA)
- [mojo-dev] [jira] (MGWT-334) Add support for Sup... Thomas Broyer (JIRA)

Don't take me on this subject; I see absolutely no advantage to be in org.codehaus.mojo. Actually, now that it's been acted that GWT will move to Maven as the build system, I'll propose to the (brand new) GWT Steering Committee that the gwt-maven-plugin be moved (or maybe rewritten from scratch, it might be easier) to GWT and com.google.gwt (just like the tomcat-maven-plugin moved to Apache), but that's another story, and it'll take time.
It appears that Nicolas De Loof unilaterally decided to move the code to GitHub a while ago, to ease contributions (and I must say it worked!), and nobody objected (quite the contrary actually): https://groups.google.com/d/msg/codehaus-mojo-gwt-maven-plugin-users/ieDbGIhqND4/g8OJAnm1G6AJ