Use an env var for the classpath of jar hell task (#48240)

The classpath for some project could outgrow the max allowed command
line on Windows. Using an env var is not fault proof, but give more
breathing room
This commit is contained in:
Alpar Torok 2019-10-22 11:16:16 +03:00
parent 3233b59b68
commit 144e8a0f1a
1 changed files with 1 additions and 1 deletions

View File

@ -42,7 +42,7 @@ public class JarHellTask extends PrecommitTask {
@TaskAction
public void runJarHellCheck() {
LoggedExec.javaexec(getProject(), spec -> {
spec.classpath(getClasspath());
spec.environment("CLASSPATH", getClasspath().getAsPath());
spec.setMain("org.elasticsearch.bootstrap.JarHell");
});
}