8d2f184389
The pain in the neck thing is, we have to use their new WAR style output, which requires us to run "mvn war:inplace" before we can start debugging, or if any dependencies change, but we also need to clean that out. All RPC handles also moved inside of the module directory, which makes it easier to debug in the hosted mode browser but breaks any existing browser client, even though the JSON payloads have not changed in format. Bug: GERRIT-75 Signed-off-by: Shawn O. Pearce <sop@google.com>
34 lines
632 B
Bash
Executable File
34 lines
632 B
Bash
Executable File
#!/bin/sh
|
|
|
|
# Builds and deploys into Jetty; primarily for debugging
|
|
|
|
jetty=$1
|
|
if [ -z "$jetty" ]
|
|
then
|
|
echo >&2 "usage: $0 jettydir"
|
|
exit 1
|
|
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=target/gerrit-*.war &&
|
|
|
|
cp $war "$jetty/webapps/gerrit.war" &&
|
|
if [ -f "$ctx" ]
|
|
then
|
|
touch "$ctx"
|
|
else
|
|
rm -f "$jetty/contexts/test.xml" &&
|
|
java -jar $war --cat extra/jetty_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
|