From a91379944accf50c8dc0082c61e399dffbd7287a Mon Sep 17 00:00:00 2001 From: jprocter Date: Mon, 9 Oct 2006 17:13:05 +0000 Subject: [PATCH] fixed log4j complaints for vamsas logging. --- src/jalview/bin/Cache.java | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/jalview/bin/Cache.java b/src/jalview/bin/Cache.java index 1050a56..1b5ba56 100755 --- a/src/jalview/bin/Cache.java +++ b/src/jalview/bin/Cache.java @@ -309,6 +309,14 @@ 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"); + 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."); } } catch (Exception e) { vamsasJarsArePresent=0; -- 1.7.10.2