Migrating from the Google Plugin for Eclipse

The Google Plugin for Eclipse does not support Eclipse 4.7 (Oxygen)
or later and is no longer available.
This document describes how to migrate a project that uses the
Google Plugin for Eclipse to supported tooling.

App Engine Standard

Cloud Tools for Eclipse supports development for the App Engine
environment.
To migrate your existing GPE project to Cloud Tools for Eclipse:

If you're using Eclipse 4.4 or earlier, upgrade to Eclipse IDE for Java EE
Developers, version 4.5 or later.

App Engine + GWT

App Engine code runs on the server, and GWT code runs on the client, though it's
compiled and served from the server. Ideally you should divide these into
separate projects: an App Engine Eclipse project and a GWT Eclipse project.

Cloud Endpoints

No IDE, Eclipse included, currently provides integrated support for Cloud
Endpoints v2. You can work with Cloud Endpoints v2 projects in Eclipse, as you
would with any other Java project. However, there are no Endpoints specific code
inspections, code generators, new project wizards, editors, or deployment tools.

If you wish to continue using Cloud Endpoints v1, you can likewise import your
backend project into Eclipse as you would any other Java project. The simplest
approach for working with Endpoints v1 without GPE is to leverage the
com.google.appengine:appengine-maven-plugin
and the Eclipse m2e integration.

If your project is not already built with maven, you need to add a pom.xml
file:

If necessary, install the m2e plugin.

Select the project in the Project Explorer.

From the context menu, select Configure > Convert to Maven Project.
This conversion adds a pom.xml file to the project and sets the project to
use the Maven builder.