Sign in

1. Products
2. Google Plugin for Eclipse

Google Plugin for Eclipse

Feedback on this document

Release Notes

• Version 3.7.0
• Version 3.6.0
• Version 3.5.1
• Version 3.5.0
• Version 3.4.2
• Version 3.4.1
• Version 3.4.0
• Version 3.3.0
• Version 3.2.4
• Version 3.2.3
• Version 3.2.2
• Version 3.2.1
• Version 3.2.0
• Version 3.1.3
• Version 3.1.2
• Version 3.1.1
• Version 3.1.0
• Version 3.0.1
• Version 2.6.0
• Version 2.5.0
• Version 1.3.3
• Version 1.3.2
• Version 1.3.1
• Version 1.3.0
• Version 1.2.0
• Version 1.1.2
• Version 1.1.1
• Version 1.1.0
• Version 1.0.1

Note: Google Plugin for Eclipse release notes for Versions 2.0 to 2.4 were combined with the GWT release notes .

Version 3.7.0

Released August 1, 2014

Features

• Support for Eclipse Luna (4.4) See Downloading and Installing the Plugin

Other Notes

• Maven Integration for App Engine has now been broken out into a separate feature. Those developers that are not interested in Maven Integration for App Engine can choose not to install it and the associated m2Eclipse dependencies.
• Maven Integration for App Engine only works with m2Eclipse 1.5+. This version of m2Eclipse is available by default on the Eclipse Luna (4.4) platform. If you'd like to install this feature on Eclipse 4.3 (Kepler) or Eclipse 4.2 (Juno), you will need to add the following update sites to your Eclipse installation:
  • http://download.eclipse.org/technology/m2e/releases
  • http://download.eclipse.org/releases/luna (needed because it has the latest version of Guava)
• If you are using GWT Designer on the Linux platform, you'll need to export SWT_GTK3=0 before running Eclipse.

Version 3.6.0

Released June 27, 2014

Features

• Support for importing App Engine Maven projects as WTP projects. See Importing an existing Maven Project

Fixes

• Issue 278 : GPE 3.5.1 incompatible with GAE SDK 1.9.4+ - Endpoint Generation Fails

Other Notes

• GPE is now compatible with ADT 23.0.0.
• GPE now requires m2e-wtp as a dependency for Eclipse 4.2 and 4.3.
• GPE no longer supports App Engine Maven projects that use the gae-maven-plugin. It only supports those that use the appengine-maven-plugin . Maven projects using the appengine-maven-plugin will be imported as WTP projects . The existing behavior of adding the GAE Nature to an App Engine Maven project is no longer supported.

Version 3.5.1

Released December 30, 2013

Fixes

• Issue 253 : GPE fails to start on Eclipse Indigo (3.7)

Version 3.5.0

Released December 20, 2013

Note: Starting with this release, the Google Plugin for Eclipse requires a Java 7 or later JDK.

Features

• Improved error reporting while generating Google cloud endpoints.
• Ability to configure the automatic launching of app engine applications in web browsers after successful deployment by checking or un-checking the "Launch app in browser after sucessful deploy" checkbox in the Deploy Project to Google App Engine dialog box.

Fixes

• Issue 238 : GWT unit tests should use -war instead of -out.
• Issue 242 : Improvement: Extend m2e connector to allow more flexible Eclipse Web Application configuration.

Version 3.4.2

Released October 14, 2013

Features

• Add support for Apps Script projects .

Version 3.4.1

Released September 13, 2013

Features

• Automatically open the URL of the App Engine application in the browser after deployment.

Fixes

• Fix for out-of-sync errors when first attempting to perform 'Run on Server' for an App Engine WTP project.
• Fix that allows user to properly run the same WTP project multiple times on the same server.

Version 3.4.0

Released September 5, 2013

Features

• Ability to select/create new App Engine Applicatioin ID when generating an App Engine project.
• Improved WTP support:
• Ability to set High Replication Datastore (HRD) settings.
• Abitity to generate Cloud Endpoints and Cloud Endpoint Client Libraries in WTP projects.
• Ability to generate a WTP-based App Engine Backend for an Android app.
• Ability to deploy a project from main toolbar.
• Improved detection of EAR support.

Fixes

• Issue 48 : GPE makes Team Synchronization Icon Decoration show then hide.
• Issue 138 : [GWT] Eclipse GWT com.google.gwt.dev.DevMode adds -XstartOnFirstThread to VM_ARGS on a Mac.
• [WTP] Fix for missing Google App Engine SDK jars during deployment.
• [WTP] Fix for Null Pointer Exception if runtime has the runtime type deleted.
• [WTP] Fix for checking version during project deployment.

Version 3.3.0

Released July 17, 2013

Features

• Support for Eclipse 4.3 (Kepler). Update site URL is: https://dl.google.com/eclipse/plugin/4.3 .
• WTP (Web Tools Platform) support for App Engine. More information can be found here .
• Adding a Google API to a Maven-based project now adds the appropriate snippet to the pom.xml file.
• If updates are available for a Google API, users can right-lick on the classpath container to update the API. Information about the update is also displayed in the 'Add Google APIs' dialog.
• Google APIs can now be added to vanilla (non-GWT and non-App Engine) Java projects.

Fixes

• Issue 195 : NoClassDefFoundError: com/google/gdt/eclipse/suite/ext/update/ui/UpdateNotificationToastPopup$NotificationControlSelectedHandler (was preventing update notifications from being displayed).
• Issue 75 : Add possibility to disable SpeedTracer in GPE.

Other changes

• Dropped support for Eclipse 3.6 (Helios). The last available release that works with 3.6 can be found here .
• remove<Entity>() method in generated Endpoints service class no longer returns a result.
• Removed com.google.gdt.eclipse.appengine.rpc plugin from the GPE distribution. This plugin was contributing the GWT RequestFactory support, but RequestFactory is now deprecated. We'll write an uninstall hook to properly uninstall this plugin in the next version of GPE.

Version 3.2.4

Released June 7, 2013

Fixes

• Issue 203 : Endpoints Example on dev app server web-side throws error when listing devices with App Engine 1.8.0.
• Issue 206 : Generate App Engine Connected Android Project option does not work with ADT 22+.

Other changes

• Client Library Dependecy upgraded to 1.15.x.
• Android Development Tools (ADT) version upgraded to to 22.x.

Version 3.2.3

Released April 26, 2013

Fixes

• Issue 117 : Errors with Cloud Endpoint Generation
• Issue 116 : Errors running builder 'Google App Engine Project Change Notifier': java.lang.NullPointerException
• Issue 111 : Wrong URL to JDK Compliance
• Issue 107 : 'Enable HRD Support' checkbox grayed out
• Issue 9214 (App Engine Tracker): GPE is not generating Endpoints Client Libraries
• Fixed a problem where Android Tools for App Engine could not be installed via Eclipse Marketplace due to missing dependency on the Android Development Tools
• Fixed Datanucleus version switching on the App Engine project properties page. The build path was not being updated after the version change was applied.

Other changes

• The Cloud Endpoints functionality now requires App Engine 1.7.7+. This applies to the "Generate App Engine Backend" and "App Engine Connected Android Project" options as well.
• Generated endpoint classes now have the ownerDomain and packagePath specified as part of the @Api annotation . They also have the API method names explicitly specified with the @ApiMethod annotation.

Version 3.2.2

Released Mar 27, 2013

Fixes

• Fixed a problem with deploying the Cloud Endpoints sample when using App Engine 1.7.6. The root URL for the endpoint would have the app version number prepended to it, which was incorrect.

Version 3.2.1

Released Mar 21, 2013

Features

• Android sample app for Cloud Endpoints now displays the last 5 messages recieved by the server.
• 'Generate App Engine Backend' and 'App Engine Connected Android Project' wizards allow the user to specify the GCM key and project number parameters.
• User is now able to choose the App Engine SDK that they'd like to use when generating an App Engine Backend or an App Engine Connected Android project. Also added detection to ensure that the user is using an App Engine SDK with version 1.7.5+.

Fixes

• Issue 83 : GWT designer doesn't work in Juno (eclipse 4.2) on Kbuntu 12.04 (64bit)
• Issue 104 : GWT Designer fails to open after update (Windows)
• Issue 106 : GWT plugin fails to initialize correctly, leaving project with build path errors
• Issue 102 : Google App Engine Project Change Notifier - NO_MODIFICATION_ALLOWED_ERR
• Fixed a variety of problems with the SDK selection of the App Engine Project Properties page:
• The datanucleus version selected by the user no longer destroys the classpath container setting in the .classpath file
• If the project is using the workspace default SDK, there will be no suffix on the classpath container reference in the .classpath file
• If the project is using the workspace default SDK, the Project Properties will actually have the 'default' option selected.
• If the user changes the workspace default SDK, the war/WEB-INF/lib directory of all affected projects will be properly updated.

Other changes

• GWT Designer updated to v3.1.3

Version 3.2.0

Released Feb 13, 2013

Features

• Updated tooling for Google Cloud Endpoints
• Support for running your App Engine application under Java 1.7 by modifying your JDK compliance level.

Fixes

• Issue 90 : Cloud Endpoints with GWT generates errors on build
• Issue 76 : GWT Compile button sometimes does nothing
• Issue 54 : Only remove/modify -javaagent parameter when dealing with a GAE project

Other changes

• Addition of paging support to the generated list* methods in Endpoint classes
• insert* methods in Endpoint classes now throw an exception if an existing primary key is passed in
• Endpoints support works with App Engine 1.7.5; previous versions of App Engine are not supported
• User is now prompted before a Web Application launch if the port is already in use
• Removed the GALGWT Maps API and the Buzz API from the 'Add Google APIs...' list
• GWT Designer updated to v3.1.2

Version 3.1.3

Released Dec 18, 2012

Fixes

• Issue 79 : Creating a GWT/App Engine project without sample code triggers a 'web.xml already exists' error
• Fixed a problem where 'Generate App Engine backend' fails if done twice (after deleting the project the first time). Error messages were appearing because there were multiple copies of the endpoint class, and a corrupted EMF class

Other changes

• Remove 'App Engine Connected Android' option completely and replace it with a 'friendly' error message. It's not working right now, and it's not ready to be released.
• Cloud Endpoints now works with App Engine 1.7.4+. App Engine 1.7.3 is no longer supported
• Cloud Endpoints not works with the Google API Client Library for Java 1.13+
• Dropped support for Eclipse 3.5. You can find older versions here

Version 3.1.2

Nov 12, 2012

Features

• Add Proguard configuration information for the Google API Client Library for Java whenever a user is using Cloud Endpoints client libraries in their Android project

Fixes

• Update generated code for App Engine backends to work with the Java API Client Library 1.12+

Version 3.1.1

Released Oct 30, 2012

Features

• Add Proguard configuration information for the Google API Client Library for Java whenever a user adds a Google API to their Android project

Other changes

• Remove 'App Engine Connected Android' option for Eclipse 3.5 and Eclipse 3.6; this feature only works in Eclipse 3.7+.

Version 3.1.0

Released August 10, 2012

Features

• Adding Google APIs for Android projects

Fixes

• Issue 77 :Cloud Endpoints does not work on the Windows

Version 3.0.1

Released June 29, 2012

Features

• Support for Eclipse 4.2 (Juno)
• Tooling for Google Cloud Endpoints.

Version 2.6.0

Released May 3, 2012

Features

• Tooling for using Java Persistence API (JPA) to access Cloud SQL
• Importing the latest Google APIs into your Google Plugin for Eclipse project
• Updating App Engine SDK

Fixes

• Issue 53 : Google Plugin for Eclipse now loads the correct projects from Google Project Hosting

Version 2.5.0

Released December 16, 2011

Features

• Tooling for Google Cloud SQL
• Support for OAuth 2.0 for authorizing the Google Plugin for Eclipse to access Google services

Fixes

• Issue 3 : Google Plugin for Eclipse doesn't expand Eclipse ${variables}
• Issue 18 : Error in loading annotation processor factory while creating an RPC service.
• Issue 22 : WebApp launch configurator architecture is broken
• Issue 23 : When JSNI start brace is partially starter method body auto completion fails
• Issue 24 : Add capability to disable JDO/JPA and not deploy those jars
• Issue 25 : Embedded browser for login broken due to Google Login UI changes
• Issue 26 : Remove use of deprecated maven-eclipse-plugin
• Issue 27 : JSNI auto-complete busted when Content Assist preference is set to 'Completion overwrites'
• Issue 28 : Unhandled event loop exception
• Issue 29 : Adding a new AppEngine SDK didn't copy jars in to WEB-INF/lib
• Issue 30 : Poor UX when adding GAE to existing GWT app - due to missing appengine-web.xml, …
• Issue 31 : Possible NPE if project has GWT Nature but no SDK

Version 1.3.3

Released June 23, 2010

Enhancements

• Support Eclipse 3.6
• Warn Java 1.5 users that future versions of App Engine will require Java 1.6

Version 1.3.1

Released March 19, 2010

Fixes

• GWT Issue 4761 : Google Plugin for Eclipse: Projects with "Launch and deploy from this directory" unchecked won't store the user's chosen directory at launch-time
• GWT Issue 4762 : Google Plugin for Eclipse: WAR argument value gets extra slashes inserted each time
• GWT Issue 4768 : Eclipse Development Mode view now shows incorrect launcher name for breadcrumb
• Expand variables used inside -war argument in launch configurations

Version 1.3.0

Released March 16, 2010

Enhancements

• Configurable WAR directory to allow better integration with Eclipse for Java EE and projects built with Maven
• Web Application launch configurations now display and allow editing of generated Program and VM arguments
• Errors/Warnings preference page for customizing the severity of any generated problem marker
• Projects can reference GWT/App Engine SDKs directly via JARs instead of through SDK library
• GWT+App Engine projects automatically configured for optimal caching

Fixes

• GWT Issue 3583 : Google Eclipse Plugin configuration is too strict
• GWT Issue 3592 : Eclipse plugin to add 'cache forever' configuration for new 'GWT + App Engine' projects
• GWT Issue 3666 : WEB-INF/lib out of sync -- change Problem from WARNING to ERROR
• GWT Issue 3902 : Allow users to configure the severity of problems reported by the eclipse plugin
• GWT Issue 4402 : suport for -startupUrl parameter in Google Eclipse plugin
• GWT Issue 4463 : "gwt-servlet.jar" Deleted at Eclipse Startup after GWT 2.0 Upgrade
• App Engine Issue 1515 : Eclipse plugin requires fixed location for war directory
• App Engine Issue 1636 : Eclipse Plugin Builder [Enhancer] Does Not Work For *.groovy *.scala etc...
• App Engine Issue 1941 : Plugin fails to enhance dependent classes on source level changes
• App Engine Issue 2115 : Using the @PersistenceAware annotation puts the Eclipse Enhancer in an Infinite Loop

For a complete list of fixed issues, see the GWT issue tracker and GAE issue tracker .

Version 1.2.0

Released December 8, 2009

Enhancements

• Support for GWT 2.0 .
• Development Mode View - inspect your debugging logs and manage the GWT code server right from Eclipse.
• UiBinder support - template editor with auto-completion, as-you-type validation of template and owner classes, and creation wizard.
• ClientBundle support - New ClientBundle wizard and as-you-type validation of ClientBundle interfaces.
• JSNI Java reference auto-completion.
• RPC interface refactoring support.

Fixes

• App Engine Issue 1937 : Unresolved import statements after updating Google Eclipse plug-in.
• App Engine Issue 1971 : Changing a project's SDK via eclipse buildclasspath dialog does not update the jars in war/WEB-INF/lib.

Version 1.1.2

Released October 13, 2009

Fixes

• GWT Issue 3923 : Web app launch configurations using OOPHM on OSX don't work (still add -XstartOnFirstThread flag)

Version 1.1.1

Released September 23, 2009

Fixes

• GWT Issue 4034 : Update the plugin to add -d32 flag if required

Version 1.1.0

Released July 30, 2009

Enhancements

• Added support for Eclipse 3.5 (Galileo).
• GWT RPC Validation with Quick Fixes - Generates errors, with quick fixes, when the sync and async interfaces don't match.
• GWT Contributor SDKs - Defines a GWT SDK that is backed by the GWT source projects in your workspace (gwt-user, gwt-dev-windows, etc).

Fixes

• App Engine Issue 1895 : App Engine classpath corruption when enabling App Engine on a project.
• GWT Issue 3537 : The plugin's GWT Compile dialog box reports 'The project {0} has errors.'
• GWT Issue 3638 : Plugin fails to refresh project file list when files change due to GWT compile
• GWT Issue 3645 : DataNucleus enhancer console steals focus every time a file is saved.
• GWT Issue 3650 : Hierarchy view causes content assist to be immediately dismissed.
• GWT Issue 3692 : Eclipse Plugin fail to compile if War is a linked folder
• GWT Issue 3693 : Eclipse Plugin JSNI validation bug: Enum:values() unknown
• GWT Issue 3727 : Google plugin for Eclipse can't find HTML files in war subdirectories
• GWT Issue 3789 : Add support for eclipse 3.5 galileo
• GWT Issue 3814 : Eclipse Plugin: GaeJreChecker$JreValidationVisitor NullPointerException
• GWT Issue 3840 : gwt eclipse plugin latest mac os x breaks java editor/compiler error reporting

For a more exhaustive list of enhancements and fixes please see the following issue tracker searches: App Engine and Google Web Toolkit .

Version 1.0.1

Released May 13, 2009

Enhancements

• New Web App Project wizard now less restrictive about the format of the project name (dots, spaces, dashes, etc. are allowed).
• GWT Compile dialog accepts custom VM arguments.
• Settings for the pre-deployment GWT compilation are now borrowed from the manually-invoked GWT compilation settings (set via GWT Compile dialog ).
• Launch configurations for App Engine-only projects now accept program arguments.
• Detailed JSP compilation failure information now printed out in the Eclipse console.

Fixes

• Modules generated by the New GWT Module wizard now contain XML declaration and module DTD reference.
• ORM enhancement is now correctly disabled when the inclusion filters list (project properties -> Google -> App Engine -> ORM) is empty.
• GWT compilation with custom generators now works correctly.
• Source and javadoc paths for GWT and App Engine SDKs have been configured.
• Errors during App Engine deployment are now more descriptive.