Announcing the Google Plugin for Eclipse 1.1.0

[Miguel Méndez]

Hi everyone,

We wanted to let all of you know that the Google Plugin for Eclipse 1.1.0 is now available.  Some of the notable improvements are:

• Support for Eclipse 3.5 (Galileo)
• GWT RPC interface validation with quick fixes
• App Engine DataNucleus enhancer console no longer steals focus on save

If you'd like more details on the contents of the release, please see the Release Notes.

To get started right way, take a look at the installation instructions or just use the update site below that corresponds to your version of Eclipse.

• Eclipse 3.5 (Galileo) - http://dl.google.com/eclipse/plugin/3.5
• Eclipse 3.4 (Ganymede) - http://dl.google.com/eclipse/plugin/3.4
• Eclipse 3.3 (Europa) - http://dl.google.com/eclipse/plugin/3.3

Cheers,

Miguel, on behalf of the Google Plugin for Eclipse Team

[Isaac Truett]

Thank you, Miguel and the plugin team, and congratulations on your
latest release!

I was amused to find that some old code in my current project
triggered the RPC interface validations (and rightly so), even though
the services were perfectly functional.

Thanks,
Isaac


2009/7/30 Miguel Méndez <mme...@google.com>:

[Miguel Méndez]

I must admit that there are some features that we forgot to include the public documentation that are specifically targeted at contributors.

The first is something that we call contributor SDKs.  These allow you to define a GWT SDK that is backed by the gwt-user, gwt-dev-PLAT/gwt-dev-oophm projects in your eclipse workspace.  Configure your workspace per http://code.google.com/p/google-web-toolkit/source/browse/trunk/eclipse/README.txt, do a single ant build to populate the staging directory, and import the gwt-user, gwt-dev-PLAT and gwt-dev-oophm projects.  Then add a new GWT SDK (you'll notice that you get an option to create an SDK uses the  GWT source projects in your workspace).

The second feature is very basic support for OOPHM.  If you are working against an SDK that supports OOPHM, you'll get a checkbox in the GWT tab of the web app launch configuration which selects between OOPHM or normal hosted mode.  Lastly, if you are on OSX and you are using an OOPHM-enabled contributor SDK, we filter the SWT jars out of the launch configuration classpath to prevent eclipse from putting -XstartOnFirstThread and breaking OOPHM.

--
Miguel

[Scott Blum]

2009/7/30 Miguel Méndez <mme...@google.com>

The first is something that we call contributor SDKs.  These allow you to define a GWT SDK that is backed by the gwt-user, gwt-dev-PLAT/gwt-dev-oophm projects in your eclipse workspace.  Configure your workspace per http://code.google.com/p/google-web-toolkit/source/browse/trunk/eclipse/README.txt, do a single ant build to populate the staging directory, and import the gwt-user, gwt-dev-PLAT and gwt-dev-oophm projects.  Then add a new GWT SDK (you'll notice that you get an option to create an SDK uses the  GWT source projects in your workspace).

The second feature is very basic support for OOPHM.  If you are working against an SDK that supports OOPHM, you'll get a checkbox in the GWT tab of the web app launch configuration which selects between OOPHM or normal hosted mode.  Lastly, if you are on OSX and you are using an OOPHM-enabled contributor SDK, we filter the SWT jars out of the launch configuration classpath to prevent eclipse from putting -XstartOnFirstThread and breaking OOPHM.

w00t, and w00t!