Overhaul our build system to only create a WAR file
We're a web application. There is no reason to create anything else
other than a single stand-alone WAR file out of our build. Using the
appjar, appdist, devdb projects all in the same repository is chaos
and difficult to maintain.
The Hudson continuous integration project has their entire WAR file
as a self-contained application, which can be run directly off the
command line with "java -jar hudson.war". This is rather nice, as
it makes it a lot easier for users to run the application code that
comes along with the web application.
This change moves everything into a single WAR file, and thus can
cut our overall download by 6 MB by reducing the copies of each
dependency JAR down from 2 (one in the .tar.bz2, one in the WAR
embedded in the .tar.bz2) to only 1 (the one in the WAR itself).
Signed-off-by: Shawn O. Pearce <sop@google.com>
diff --git a/appjar/src/main/java/log4j.properties b/appjar/src/main/java/log4j.properties
index b156415..051f623 100644
--- a/appjar/src/main/java/log4j.properties
+++ b/appjar/src/main/java/log4j.properties
@@ -8,3 +8,8 @@
#
log4j.logger.org.apache.sshd.common=WARN
log4j.logger.org.apache.sshd.server=WARN
+
+# Silence non-critical messages from c3p0 (if used).
+#
+log4j.logger.com.mchange.v2.c3p0=WARN
+log4j.logger.com.mchange.v2.resourcepool=WARN
