@Brandon so GPE is going to be like Chrome, and gwt-eclipse-plugin will be like Chromium?
On Tuesday, June 30, 2015 at 3:18:24 PM UTC-4, Brandon Donnelson wrote: > > The plugin has been forked although it still has the App Engine features. > Although the Google login isn't working on the GWT plugin for Eclipse at > the moment. Eventually we should see a Eclipse plugin that only has the > Google features and the GWT features can live on there own, yet both will > come together to do the same thing. GPE is closed source, although the fork > has all of its source plus some more. The Fork is a community version and > can accept patches where GPE is closed and can not at this time. > > Does that help? > > Thanks, > Brandon > > On Tuesday, June 30, 2015 at 10:55:10 AM UTC-7, Joel Handwell wrote: >> >> That means >> 1. Google Plugin for Eclipse will change its name to GWT Eclipse Plugin? >> (then the name I think does not include features like App Engine SDK) >> or >> 2. Google Plugin for Eclipse will be continued to be closed source, and >> GWT Eclipse Plugin will be developed as fork independent from GPE? >> >> On Tuesday, June 30, 2015 at 4:58:06 AM UTC-4, Jens wrote: >>> >>> >>> As of 2015 June 29, Eclipse 4.5 is available. Any updates about GPE on >>>> github ? >>>> >>> >>> https://github.com/gwt-plugins/gwt-eclipse-plugin >>> >>> This is an open source fork of the original GPE. >>> >>> -- J. >>> >> -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/3e3ec520-add8-443d-af70-7e3a5e15ee07%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
