Max Rydahl Andersen [http://community.jboss.org/people/maxandersen] modified the blog post:
"Thoughts on Google Eclipse Plugins going Open Source" To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/11/16/thoughts-on-google-eclipse-plugins-going-open-source -------------------------------------------------------------- Google http://googlewebtoolkit.blogspot.com/2011/11/google-plugin-for-eclipse-gpe-is-now.html today announced they are making http://code.google.com/p/google-plugin-for-eclipse/ “Google Plugin for Eclipse” and http://code.google.com/p/gwt-designer/ "GWT Designer" fully open source and available under the Eclipse Public license. We have many developers using Google’s Eclipse plugin to develop GWT-based applications targeting the JBoss Application Server. With the open sourcing of the plugin we are looking forward to working even more closely with the Google team and the rest of the community on making the developer experience even more productive and an integrated part of Eclipse platform. We are especially interested in seeing the Google Eclipse plugins being able to target multiple runtimes such as the JBoss Enterprise Application Platform and Google App Engine in a uniform way, working more seamlessly with standards-based tools and frameworks. This targeting of multiple runtimes will also help users of JBoss AS, Glassfish, Tomcat and any other server that provides an Eclipse Web Tools compatible server adapter. h1. JBoss Tools GWT Integration JBoss Tools already provide integration with the previous release of GPE via our experimental http://community.jboss.org/docs/DOC-15794 JBoss GWT Integration. Our experimental plugin allows you to easily use the Eclipse standard web wizards and projects instead of the Google specific wizards to create and deploy projects. One of the reasons we marked this integration “experimental” was because opposite to what many believe large parts of Google’s plugins for Eclipse was not open sourced. That made the implementation dependent on non-public API and to use it you needed the GPE GWT plugins that was not possible to distribute freely. Those concerns were the reasons I’ve been urging Google to make the GWT plugins open source so we and users could actually distribute and use the plugins freely and at the same time we could start contributing fixes and features and not just bugreports. In the end this should allow for much more stable and uniform user experience. This goes not only for JBoss Tools plugins integration, but for integration across the Eclipse ecosystem such as Eclipse Web Tools Project and m2eclipse. Some of the issues we had, have been fixed in GPE 2.0. Now with Google open sourcing their plugin we and others can help contribute and fix the remaining issues and implement enhancements to make easy usage of Google GWT across multiple platforms from Eclipse a reality. None of this of course happen automatically but the open sourcing of the Google plugins definitely make it much easier and I look forward to see and support the work around these plugins. Thank you Google - now let’s go and have Fun :) -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/community/tools/blog/2011/11/16/thoughts-on-google-eclipse-plugins-going-open-source]
_______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
