Problem: gae:start not forking

Since the string that is printed out by the local appengine server has changed, we need to watch for it instead. We change the string to "is running" to be a bit more robust in the future as well.
Problem: GAE 1.7.5 doesn't run with certain javaAgents

As described at https://code.google.com/p/appengine-maven-plugin/issues/detail?id=10, there can be problems with adding the "noverify" flag when also specifying a javaAgent to the server. Instead, we provide an option which will allow you to *not* add this flag, if it's causing problems.
Update to GAE 1.7.6

Build the gae-runtime against version 1.7.6, which was released by Google recently.
Merge pull request #75 from toonetown/feature/server-noverify

Problem: GAE 1.7.5 doesn't run with certain javaAgents
Merge pull request #76 from toonetown/feature/server-start-forking

Problem: gae:start not forking
Merge pull request #77 from toonetown/feature/update-1.7.6

Update to GAE 1.7.6
Home Readme has been updated to cleary identify how to setup the Mavnen
Plugin configuration so it no longer depends on the built-in gae-runtime
which is nearly always out of date.
Updated readme comments
Merge pull request #80 from maven-gae-plugin/brandon_home_readme_update

Home Readme.md update
Revert "Problem: GAE 1.7.5 doesn't run with certain javaAgents"

This reverts commit 2acb32ec7b8fa8ff2a7239ac55a24fe37f19dc18.
Avoid IF nesting, keeping the backwards compaitibility of the origina patch (2acb32ec7b8fa8) and still allows people to cleanly override the -noverify behavior
Fix noVerify parameter documentation
Update new upload url
typo
Update README.md

Tune the Readme doc version configuration params. 
Update README.md
Update README.md
Update README.md

Adding configuration for gae integration testing. 
Update README.md

Formatting fix of maven integration testing section. 
Update README.md

Changing 1.7.6 to 1.7.7