*Always* use the context class loader

If we ever limit which class loader we use as parent or to discover the
available dependencies by using the class loader that happened to load
MiniMaven, we will be in for a *lot* of trouble in the future, e.g. with
ImageJ 1.x' PluginClassLoader.

So let's not do that. Let's use the current thread's context class loader,
like everywhere else we need a class loader.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Author: dscho

src/main/java/org/scijava/plugins/scripting/java/JavaEngine.java

@@ -168,7 +168,7 @@ public Object eval(Reader reader) throws ScriptException {
 					urls[i] = new URL("file:" + paths[i]
 							+ (paths[i].endsWith(".jar") ? "" : "/"));
 				URLClassLoader classLoader = new URLClassLoader(urls,
-						getClass().getClassLoader());
+						Thread.currentThread().getContextClassLoader());
 
 				// needed for sezpoz
 				Thread.currentThread().setContextClassLoader(classLoader);
@@ -608,7 +608,8 @@ private static Element append(final Document document, final Element parent, fin
 	 */
 	private static List<Coordinate> getAllDependencies(final BuildEnvironment env) {
 		final List<Coordinate> result = new ArrayList<Coordinate>();
-		for (ClassLoader loader = env.getClass().getClassLoader(); loader != null; loader = loader.getParent()) {
+		for (ClassLoader loader = Thread.currentThread().getContextClassLoader();
+				loader != null; loader = loader.getParent()) {
 			if (loader instanceof URLClassLoader) {
 				for (final URL url : ((URLClassLoader)loader).getURLs()) {
 					if (url.getProtocol().equals("file")) {