From 6ccdee6ace7479352a58c4931f312d9ae3a7e50a Mon Sep 17 00:00:00 2001
From: Sean Flanigan <sflaniga@redhat.com>
Date: Thu, 14 May 2015 17:29:22 +1000
Subject: [PATCH] Add workaround for Liquibase CORE-2024

---
 .../jetty/server/handler/AbstractHandler.java   | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 zanata-war/src/main/java/org/eclipse/jetty/server/handler/AbstractHandler.java

diff --git a/zanata-war/src/main/java/org/eclipse/jetty/server/handler/AbstractHandler.java b/zanata-war/src/main/java/org/eclipse/jetty/server/handler/AbstractHandler.java
new file mode 100644
index 0000000000..f1f1adb466
--- /dev/null
+++ b/zanata-war/src/main/java/org/eclipse/jetty/server/handler/AbstractHandler.java
@@ -0,0 +1,17 @@
+package org.eclipse.jetty.server.handler;
+
+import lombok.extern.slf4j.Slf4j;
+
+/**
+ * Workaround for unwanted logging caused by Liquibase.
+ * http://stackoverflow.com/questions/26530677/why-failed-to-define-class-warn-from-server-startup.
+ * https://liquibase.jira.com/browse/CORE-2024.
+ *
+ * @author cilap http://stackoverflow.com/a/29942016/14379
+ */
+@Slf4j
+// TODO Remove when Liquibase CORE-2024 is fixed
+public class AbstractHandler {
+   public AbstractHandler() {
+   }
+}