Removed logging code from DirectoryClassLoader

The class loader is instantiated before dynamically loaded jars are
added. This means, if the slf4j backend implementation is loaded using
this mechanism (which should be the default), the backend is not yet
available when the DirectoryClassLoader is created. This will cause
slf4j to use the no operation logger which is not what the user expects.

Author: cboehme

src/main/java/org/culturegraph/mf/runner/util/DirectoryClassLoader.java

@@ -21,8 +21,7 @@
 import java.net.URL;
 import java.net.URLClassLoader;
 
-import org.slf4j.Logger;
-import org.slf4j.LoggerFactory;
+import org.culturegraph.mf.exceptions.MetafactureException;
 
 /**
  * A class loader which allows adding directories to the class
@@ -33,8 +32,6 @@
  */
 public final class DirectoryClassLoader extends URLClassLoader {
 
-	private static final Logger LOG = LoggerFactory.getLogger(DirectoryClassLoader.class);
-
 	private static final String JAR_FILE_EXTENSION = ".jar";
 	private static final String CLASS_FILE_EXTENSION = ".class";
 
@@ -53,13 +50,11 @@ public DirectoryClassLoader(final ClassLoader parent) {
 	}
 
 	public void addDirectory(final File dir) {
-		LOG.info("Adding jar and class files in {} to class loader", dir);
 		for (final File file : dir.listFiles(JAR_AND_CLASS_FILTER)) {
 			try {
-				LOG.info("Adding {} to class loader", file);
 				addURL(file.toURI().toURL());
 			} catch (final MalformedURLException e) {
-				LOG.error("Could not add {} to class loader: {}", file, e);
+				throw new MetafactureException("Could not add " + file + " to class loader", e);
 			}
 		}
 	}