let IDEs have jar hell in tests

This commit is contained in:
Robert Muir 2015-07-01 14:29:57 -04:00
parent 41ac191cac
commit 976ace21e0
1 changed files with 8 additions and 1 deletions

View File

@ -25,6 +25,7 @@ import org.elasticsearch.bootstrap.ESPolicy;
import org.elasticsearch.bootstrap.Security; import org.elasticsearch.bootstrap.Security;
import org.elasticsearch.common.Strings; import org.elasticsearch.common.Strings;
import org.elasticsearch.common.io.PathUtils; import org.elasticsearch.common.io.PathUtils;
import org.elasticsearch.common.logging.Loggers;
import java.io.FilePermission; import java.io.FilePermission;
import java.nio.file.Path; import java.nio.file.Path;
@ -55,7 +56,13 @@ public class BootstrapForTesting {
try { try {
JarHell.checkJarHell(); JarHell.checkJarHell();
} catch (Exception e) { } catch (Exception e) {
if (Boolean.parseBoolean(System.getProperty("tests.maven"))) {
throw new RuntimeException("found jar hell in test classpath", e); throw new RuntimeException("found jar hell in test classpath", e);
} else {
Loggers.getLogger(BootstrapForTesting.class)
.warn("Your ide or custom test runner has jar hell issues, " +
"you might want to look into that", e);
}
} }
// make sure java.io.tmpdir exists always (in case code uses it in a static initializer) // make sure java.io.tmpdir exists always (in case code uses it in a static initializer)