Add JettyServer to serve static HTML. Replace Server.java.
Add Jetty plugins. Modify Jetty version
Retabbed pom.xml file

We use 4-spaces instead of tabs in pom.xml. @smishra2's commit had tab
characters.
Reformatting of Jetty code to match guidelines

We have coding guidelines on the wiki:
<https://github.com/routemaster/routemaster-frontend/wiki/Coding-Guidelines>

My modifications were:

- Use spaces not tabs
- Use same-line curly braces (not explicitly in the guidelines, but in
  the code samples)
- Wrap to 80 columns
Merge pull request #13 from routemaster/features/webserver-reformatted

Reformatted Webserver Code
Update version of Jetty

We were on an awfully old version of Jetty. Now instead of that, and
instead of the RC for the 9.x series, we're on the latest stable version
of Jetty 8.x.

This doesn't appear to break anything.
Make Jetty use the jarfile's path

Previously, the webserver was loading content from the current working
directory. This reworks some code so that we form an actual object so
that we can get access to the class loader, but I think it's actually a
positive move regardless.

Now, going to localhost:8080 should serve the demo.html file to you. You
can change the url by hand for now to get to our other html files.
Use camelCase everywhere in JettyServer

While I personally enjoy under_scores, it's not the convention in Java,
and "when in Rome, do as the Romans do".
Remove Servlet, because we aren't using it

It'll still be in the commit history, and it may be useful in the
JSON-serving backend component, but since we're only serving static
content, it doesn't make sense here.
Get rid of unused imports in JettyServer
Enable logging, and use log4j

log4j is Apache's logger. It gives us tons of stuff we'll never use, but
it's simple enough to install with Maven, so why not?
Merge pull request #15 from routemaster/features/webserver-bugfixes

Features/webserver bugfixes
Merge pull request #19 from routemaster/webserver

Add minimal Jetty webserver