From 57677416c9d03530e3cbe373fc9bf40c1df2eb38 Mon Sep 17 00:00:00 2001 From: jprocter Date: Mon, 9 Oct 2006 17:15:57 +0000 Subject: [PATCH] fixed log4j complaints for vamsas logging (again) --- src/jalview/bin/Cache.java | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/jalview/bin/Cache.java b/src/jalview/bin/Cache.java index 1b5ba56..32a11e2 100755 --- a/src/jalview/bin/Cache.java +++ b/src/jalview/bin/Cache.java @@ -309,11 +309,10 @@ public class Cache if (jalview.jbgui.GDesktop.class.getClassLoader().loadClass("org.vamsas.client.VorbaId")!=null) { jalview.bin.Cache.log.debug("Found Vamsas Classes (org.vamsas.client.VorbaId can be loaded)"); vamsasJarsArePresent=1; - Logger lvclient = Logger.getLogger("org.vamsas.client"); + Logger lvclient = Logger.getLogger("org.vamsas"); lvclient.setLevel(Level.toLevel(Cache.getDefault("logs.Vamsas.Level", Level.INFO.toString()))); - ConsoleAppender ap = new ConsoleAppender(new SimpleLayout(), - "System.err"); + lvclient.addAppender(log.getAppender("JalviewLogger")); // Tell the user that debug is enabled lvclient.debug("Jalview Vamsas Client Debugging Output Follows."); -- 1.7.10.2