fixed log4j complaints for vamsas logging (again)

diff --git a/src/jalview/bin/Cache.java b/src/jalview/bin/Cache.java
index 1b5ba56..32a11e2 100755 (executable)
--- 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.");