Google Cloud Platform

Google is bringing new alternative to standard Google App Engine environments: Java, Python, GO, and PHP. Now you will be no more constrained to any predefined development environment / language -  you can configure your own Managed VM using Docker. Managed VM will be spawn on demand to handle your application traffic in similar way as Google App Engine instances are spawn. But using Managed VM you will be able to develop application using any language and environment you want. Now Managed VMs (aka GAE 2.0) are in Beta phase - see docs: https://cloud.google.com/appengine/docs/managed-vms/

To start developing Google App Engine applications you will need: Java SDK 1.7( download ) Eclipse Luna J2EE (Windows: 64-bit or 32-bit , Linux: 64-bit or 32-bit ) Google plugin for Eclipse (may be installed from update site: https://dl.google.com/eclipse/plugin/4.4 ) Maven v. 3.1 or higher (download Maven 3.2.3 ) Run command to generate GAE project using Maven $ mvn archetype:generate -Dappengine-version=1.9.22 -Dapplication-id= your-app-id -Dfilter= com.google.appengine.archetypes: Then select : 1: remote -> com.google.appengine.archetypes:appengine-skeleton-archetype (A skeleton application with Google App Engine) Then use lastest available  archetype version : Choose com.google.appengine.archetypes:appengine-skeleton-archetype version:  1: 1.8.7 2: 2.0.0-1.9.10 3: 2.0.1-1.9.20 4: 2.0.2-1.9.21 $ mvn archetype:generate -Dappengine-version=1.9.22 -Dapplication-id= guestbook -Dfilter=com.google.appengine.archety...

Since February 2014, Google App Engine doesn't allow to redeploy applications compiled at Java 1.6 compliance level. Every project must be updated to Java 1.7 compliance level before (re)deployment.   It may seem to be a simple task described here: https://developers.google.com/eclipse/docs/jdk_compliance, but i f you are using Eclipse you may experience problems. Looks like there is some problem to update compliance level using Eclipse plugin -  not every GAE SDK version can be easily updated to 1.7 compliance level . From my experience update doesn't work with GAE SDK 1.7.0 ( notice: GAE SDK version - not Java 1.7 ) or lower. I haven't evaluated which GAE version is the lowest one that allows migration to Java 1.7, but I've figured out that it can be done using GAE 1.8.7 Problem with migration is probably related to GAE SDK / Eclipse plugin for GAE.