On Dec 12, 1:08 am, Geoffrey Wiseman geoffrey.wise...@gmail.com
wrote:
On Dec 11, 2:14 pm, Rajeev Dayal rda...@google.com wrote:
We did not opt for this approach for simplicity's sake. Since we were
planning on maintaining backwards compatibility with previous SDK versions,
there was no
Yes, I'd say it's worth filing as an enhancement. That's a legitimate point.
On Mon, Dec 14, 2009 at 1:04 PM, Geoffrey Wiseman
geoffrey.wise...@gmail.com wrote:
On Dec 12, 1:08 am, Geoffrey Wiseman geoffrey.wise...@gmail.com
wrote:
On Dec 11, 2:14 pm, Rajeev Dayal rda...@google.com wrote:
On Fri, Dec 11, 2009 at 8:27 PM, Javier jasand...@gmail.com wrote:
Rajeev, thanks for your reply.
You can use the Google Plugin for Eclipse 1.2 with GWT 1.7 - they are
compatible.
If this is the case, I don't care at all about which GPE version is
exposed via the update site, so long as
Hello there:
our current project uses GWT 1.7.1 and, for a variety of reasons, we
don't want to upgrade to 2.0.0 yet.
I'd like to setup our current development environment on a new
machine; I'm at the point where I need to install the GWT eclipse
plugin, but when I go to the update site
You can use the Google Plugin for Eclipse 1.2 with GWT 1.7 - they are
compatible. So, you can install the latest plugin from the update side BUT
exclude the installation of the SDK. Even if you did install the SDK, it
does not automatically change your project over to use the new one, so you
would
We did not opt for this approach for simplicity's sake. Since we were
planning on maintaining backwards compatibility with previous SDK versions,
there was no good reason to provide older versions of the plugin for
installation.
If it is ever the case that we release a version of the plugin that
Rajeev, thanks for your reply.
You can use the Google Plugin for Eclipse 1.2 with GWT 1.7 - they are
compatible.
If this is the case, I don't care at all about which GPE version is
exposed via the update site, so long as it works with GWT 1.7.1. So
GPE 1.2 will work for me.
So, you can
On Dec 11, 2:14 pm, Rajeev Dayal rda...@google.com wrote:
We did not opt for this approach for simplicity's sake. Since we were
planning on maintaining backwards compatibility with previous SDK versions,
there was no good reason to provide older versions of the plugin for
installation.
That
