Adding property to specify deployment account.

Update README instructions as well.

Change-Id: I7fbc886d3af443f4c33fbea489e01e6e4ee71616
diff --git a/README.md b/README.md
index 7fa0824..e4610d4 100644
--- a/README.md
+++ b/README.md
@@ -1,37 +1,52 @@
 
-- gwt-site-webapp
+- **gwt-site-webapp**.
  This project includes the server an client code of the GWT site
  It does not include the site content which is in the gwt-site project
  nor the utilities for uploading the documentation to GAE Servers which
  are in the gwt-site-uploader project.
 
-- Requirements
- [Apache Maven](http://maven.apache.org) 3.0 or greater, and JDK 6+ in order to run.
+- **Requirements**
+ [Apache Maven](http://maven.apache.org) 3.0 or greater, and JDK 7+ in order to run.
 
-- Before building the project you may need gwt-site packaged file.
-  Go to the gwt-site folder and run:
-  $ mvn install
+- Before building the project you may need **gwt-site** packaged file.
+  Go to the `gwt-site` folder and run:
 
-- To build and check the app, run
-  $ mvn package
+        $ cd [...]/gwt-site
+        $ mvn install
 
-  Now you can point your browser to the target/www folder or you can deploy
-  its content in any web-server.
+- To **build** and check the app, run
 
-- Building will run the tests, but to explicitly run tests you can use the test target
-  $ mvn test
+        $ cd [...]/gwt-site-webapp
+        $ mvn package
 
-- Develop and Deploy in GAE
-  This app is thought to be run in GAE servers, so it comes with all dependencies for it.
+  Now you can point your browser to the `target/www` folder or you can serve
+  its content with any web-server (i.e [serve](https://www.npmjs.com/package/serve)).
+  Notice that the second way is needed if you want to test site navigation via Ajax.
 
-  To start the app, use the [App Engine Maven Plugin](http://code.google.com/p/appengine-maven-plugin/)
-  that is already included in this project. Just run the command:
-  $ mvn appengine:devserver
+- Building will run the **tests**, but to explicitly run them you can use the test target
 
-  You might upload the gwt stuff to the dev server, just open another terminal, 
-  go to the gwt-site-uploader folder project and run:
-  $ sh upload.sh localhost
+        $ mvn test
 
-  For further information about GAE, consult the [Java App Engine](https://developers.google.com/appengine/docs/java/overview) documentation.
-  To see all the available goals for the App Engine plugin, run
-  $  mvn help:describe -Dplugin=appengine
+- **Develop and Deploy**. This app is thought to be run in GAE servers, so it comes with all dependencies for it.
+
+  * To start the app using the [App Engine Maven Plugin](http://code.google.com/p/appengine-maven-plugin/) included in this project, just run the command:
+
+            $ mvn appengine:devserver
+
+  * You might upload the gwt stuff to the local developer server, just open another terminal,
+  go to the `gwt-site-uploader` folder project and run:
+
+            $ cd [...]/gwt-site-uploader
+            $ sh upload.sh localhost
+
+  * If you wanted to deploy to production, you might change the `<application>` section in the
+  `src/main/webapp/WEB-INF/appengine-web.xml` to point to the appropriate GAE instance and
+  then deploy to Google servers running:
+
+            $ mvn appengine:update -DgaeAccount=your_google_account
+
+  * For further information about GAE, consult the [Java App Engine](https://developers.google.com/appengine/docs/java/overview) documentation.
+
+      To see all the available goals for the App Engine plugin, run
+
+            $ mvn help:describe -Dplugin=appengine
diff --git a/pom.xml b/pom.xml
index 9b2bfff..be0a0ce 100644
--- a/pom.xml
+++ b/pom.xml
@@ -178,6 +178,10 @@
                 <configuration>
                     <version>${appengine.app.version}</version>
                     <address>0.0.0.0</address>
+                    <email>${gaeAccount}</email>
+                    <oauth2>false</oauth2>
+                    <noCookies>true</noCookies>
+                    <passin>true</passin>
                 </configuration>
             </plugin>