From 21b070c1ba841fc688ad164bc45b13482588e493 Mon Sep 17 00:00:00 2001 From: Sean Flanigan Date: Mon, 29 Feb 2016 11:56:24 +1000 Subject: [PATCH] Upgrade Liquibase, remove workaround for startup warnings --- pom.xml | 2 +- zanata-war/pom.xml | 2 +- .../jetty/server/handler/AbstractHandler.java | 17 ----------------- 3 files changed, 2 insertions(+), 19 deletions(-) delete mode 100644 zanata-war/src/main/java/org/eclipse/jetty/server/handler/AbstractHandler.java diff --git a/pom.xml b/pom.xml index 61fadc8c1d..91f30f4622 100644 --- a/pom.xml +++ b/pom.xml @@ -562,7 +562,7 @@ org.liquibase liquibase-core - 3.4.1 + 3.4.2 diff --git a/zanata-war/pom.xml b/zanata-war/pom.xml index 6dd4f9a123..43949381c4 100644 --- a/zanata-war/pom.xml +++ b/zanata-war/pom.xml @@ -2197,7 +2197,7 @@ com.mattbertolini liquibase-slf4j - 1.2.1 + 2.0.0 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 deleted file mode 100644 index f1f1adb466..0000000000 --- a/zanata-war/src/main/java/org/eclipse/jetty/server/handler/AbstractHandler.java +++ /dev/null @@ -1,17 +0,0 @@ -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() { - } -}