Remove legacy tools/to_jetty.sh

This only existed for developers to bundle their WAR and move
it into their external Jetty container for testing.  Now that
we have our own internal daemon, we really prefer this for any
development work because its self-contained and starts up faster.
Its also implemented by Jetty and is easier to upgrade, making it
more likely we'll be running current stable, patched code.

Change-Id: I00ce142c9ca1009ff49e3ff70f3c977d3c50866e
Signed-off-by: Shawn O. Pearce <sop@google.com>

tools/to_jetty.sh

@@ -1,38 +0,0 @@
-#!/bin/sh
-
-# Builds and deploys into Jetty; primarily for debugging
-
-jetty=$1
-if [ -z "$jetty" ]
-then
-        if [ -z "$JETTY_HOME" ]
-        then
-                echo >&2 "usage: $0 jettydir"
-                exit 1
-        fi
-        jetty=$JETTY_HOME
-fi
-if ! [ -f "$jetty/etc/jetty.xml" ]
-then
-	echo >&2 "error: $jetty is not a Jetty installation"
-	exit 1
-fi
-
-ctx="$jetty/contexts/gerrit.xml" &&
-
-mvn clean package &&
-war=gerrit-war/target/gerrit-*.war &&
-extra=gerrit-war/src/main/webapp/WEB-INF/extra/ &&
-
-cp $war "$jetty/webapps/gerrit.war" &&
-if [ -f "$ctx" ]
-then
-	touch "$ctx"
-else
-	rm -f "$jetty/contexts/test.xml" &&
-	cp "$extra/jetty6/gerrit.xml" "$ctx" &&
-
-	echo >&2
-	echo >&2 "You need to copy JDBC drivers to $jetty/lib/plus"
-	echo >&2 "You need to edit and configure $ctx"
-fi