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.
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
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
@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
As of 2015 June 29, Eclipse 4.5 is available. Any updates about GPE on
github ?
On Friday, July 4, 2014 at 11:36:40 AM UTC-4, Brandon Donnelson wrote:
I hear there is a build coming for Eclipse Luna but don't know about a
release date yet.
On Thursday, July 3, 2014 9:21:07 PM UTC-7,
I hear there is a build coming for Eclipse Luna but don't know about a
release date yet.
On Thursday, July 3, 2014 9:21:07 PM UTC-7, Benjamin Hill wrote:
Any luck? Would love to try with Eclipse 4.4, was hoping that the dev
build worked.
On Sunday, December 8, 2013 3:11:44 PM UTC-8,
I'm interested in helping get the support for GAE 1.8.8 with maven working.
It's not setting up the sdk directory correctly when maven is used. I've
also like to add better feature support for added vm attributes down the
road. I'd like to add some more error checking for jdo/jpa datanuclueus
Any new when the repo will be public.
I would love to build some stuff on top of GPE.
2013/12/8 Brandon Donnelson branflake2...@gmail.com
I'm interested in helping get the support for GAE 1.8.8 with maven
working. It's not setting up the sdk directory correctly when maven is
used. I've also
On Sunday, December 8, 2013 11:26:41 PM UTC+1, Alain Ekambi wrote:
Any new when the repo will be public.
I would love to build some stuff on top of GPE.
The GPE repo is already public, just not on GitHub (and still using SVN):
I know the source is open. But last time I checked it was nt possible to
build it.
I still cant find any information about how to build the plugin.
Is that available somewhere ?
2013/12/8 Thomas Broyer t.bro...@gmail.com
On Sunday, December 8, 2013 11:26:41 PM UTC+1, Alain Ekambi wrote:
I have no idea how one builds Eclipse plugins but I suspect (in this case)
this is Eclipse driven (i.e. no Ant or similar command-line-oriented
build tool)
On Sunday, December 8, 2013 11:41:09 PM UTC+1, Alain Ekambi wrote:
I know the source is open. But last time I checked it was nt possible
Hey guys,
The source is on SVN, as Thomas says, but it's not up-to-date nor is it
buildable right now.
We have a hidden project on GitHub with the updated GPE source, but I don't
want to open it up until external people can actually build it. I'm working
on this as we speak. I'd expect to have
Hi Brandon,
The sources are on GitHub right now, but they are not public. I'm working
on externalizing the build system. I don't want to make the sources public
till then, as it's not much use to outside contributors if they can't build
the plugin themselves (which has been evidenced by the GPE
Rajeev, could I ask what the status is on the project? Maybe it's premature
to ask yet. :) I'd like to see if I can plugin to contribute.
Brandon Donnelson
On Thursday, October 31, 2013 12:54:21 PM UTC-7, Jens wrote:
As for the problem you've noted, I'll fix that up this week and we'll aim
I assume there is no workaround whilst we are waiting for GPE to be updated
for 2.6 ??
G
On Wednesday, 30 October 2013 20:22:33 UTC+10, Jens wrote:
We are start using GWT trunk builds for development but Eclipse / GPE
always says GWT SDK ... on the projects build path is not valid (Version
There is a workaround - I'm on my phone now, but I posted it in the bug
report. Essentially you can tell the plugin to not worry about invalid
SDKs, and either mark then as merely errors, or just ignore it entirely.
With that set, we've noticed no other I'll effects so far.
On Nov 17, 2013 12:29
Hey Stephen,
We're in the process of moving the GPE source to github (and converting the
build system to Maven/Tycho so that external developers can build it) ,
which is why that repo hasn't been updated in a long time. I'll update the
homepage to reflect that.
As for the problem you've noted,
Hi Rajeev,
Good to hear from you.
We're in the process of moving the GPE source to github (and
converting the build system to Maven/Tycho so that external
developers can build it) , which is why that repo hasn't been updated
in a long time. I'll update the homepage to reflect that.
Sounds
As for the problem you've noted, I'll fix that up this week and we'll aim
to put out a release that works with GWT trunk in the next two weeks.
Sounds great. Thanks a lot!
-- J.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you
Looks like commit
https://gwt.googlesource.com/gwt/+/db1b5bc561c3a4826002447b88401d626dc750bf
breaks the current Google Eclipse Plugin's SDK version detection as it
probably checks against the removed GWT_VERSION field. So GWT 2.6 probably
also needs a GPE update.
-- J.
--
Luckily the mechanism of Googles Eclipse Plugin to detect GWT Maven
dependencies does not do the version check. So as a workaround I can remove
the GWT facet, add GWT libraries manually and re-add the GWT facet on the
project. The plugin then accepts the manually added GWT libraries as GWT
And as a nit pick:
While searching for the reason for the problem I noticed that @GWT_SVNREV@
has been changed to @GWT_GITREV@
in https://gwt.googlesource.com/gwt/+/05c7aeb80335bb834659176989d0d984b01da2c8
But the files
distro-source/core/src/
about.html
about.txt
have not been updated
Luckily the mechanism of Googles Eclipse Plugin to detect GWT Maven
dependencies does not do the version check. So as a workaround I can remove
the GWT facet, add GWT libraries manually and re-add the GWT facet on the
project. The plugin then accepts the manually added GWT libraries as
For
reference:
https://code.google.com/p/google-plugin-for-eclipse/issues/detail?id=246
-- J.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this
have not been updated to @GWT_GITREV@.
Thanks! Good catch.
https://gwt-review.googlesource.com/#/c/5194/
- Stephen
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
---
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To
I was going to ask how active the GPE project is...is the last commit
really from October 2012?
https://code.google.com/p/google-plugin-for-eclipse/source/list
That doesn't seem right, but AFAICT there isn't another source repo?
https://developers.google.com/eclipse/community
- Stephen
--
26 matches
Mail list logo
