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:
parent
3233b59b68
commit
144e8a0f1a
|
@ -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");
|
||||
});
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue