Delete pom.xml
Add Mousetrap for handling keyboard shortcuts

* Switch modal to use Mousetrap for “esc” rather than custom binding
* Bind to “c” globally for creating a new application
* Bind to “#” when the app modal is open to delete the app
Consolidate Mousetrap binding to top level

The top level “App” should be the dispatcher for keyboard events.
Centralize modal behavior into Marathon component

* Remove NewAppButtonComponent; it’s just a simple button
* Create “Marathon” component, which is the root of the application
* Move control of the new app modal into the application rather than
  the button (a button shouldn’t own a modal)
Let NewAppModal instantiate its own model

This means the instaniator can do whatever it wants with the App
including nothing. The NewAppModal now has control of its modal and
passes it back onCreate, which encapsulates the model creation.
Remove unused Mousetrap reference
Remove duplicate 'mixins' declaration from AppModalComponent
Merge pull request #326 from mesosphere/mousetrap-key-bindings

Mousetrap key bindings
Use our execution context and the configured ZK timeout everywhere.
Point to proper directory for main.js
Compiling sources
Link to current version in README
Move java files to src/main/java
Master is now 0.6
add jersey servlet as dependency
Fix start script
add build info
Allow arbitrary JVM options to be passed to marathon

The current start script only passes -D options as a command line parameter
to the JVM. This makes it impossible to use e.g. -agentlib or -agentpath or
the various -X options.

This change allows using an environment variable (JVM_OPTS) to contain these
options and have them passed directly to the JVM.

E.g. to start marathon with a tuned garbage collector and memory setting:

JVM_OPTS="-Xmx128m -XX:+UseConcMarkSweepGC -XX:+ExplicitGCInvokesConcurrent -XX:+AggressiveOpts -XX:+HeapDumpOnOutOfMemoryError" ./bin/start <marathon options>
Merge pull request #331 from hgschmie/master

Allow arbitrary JVM options to be passed to marathon
Update Tomcat example to include a WAR