You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Windows, there is a limit for command line length. When having much dependencies, one hits this limit. A workaround is to convert the --module-path argument into a file (which is a Command-Line Argument File). This is done by the Classpath to File Gradle Plugin.
The gradle team also thought of solutions, but there is no progress (see gradle/gradle#1989).
The "simple" workaround at gradle/gradle#1989 (comment) does not work: The jar files are not found by gradle-modules-plugin.
I wonder whether org.javamodularity.moduleplugin.tasks.RunTaskMutator#updateJavaExecTask can be patched to shorten the command line? I would propose to use "Solution 1" of gradle/gradle#10114 (comment).
The text was updated successfully, but these errors were encountered:
On Windows, there is a limit for command line length. When having much dependencies, one hits this limit. A workaround is to convert the
--module-path
argument into a file (which is a Command-Line Argument File). This is done by the Classpath to File Gradle Plugin.The gradle team also thought of solutions, but there is no progress (see gradle/gradle#1989).
The "simple" workaround at gradle/gradle#1989 (comment) does not work: The
jar
files are not found bygradle-modules-plugin
.I wonder whether
org.javamodularity.moduleplugin.tasks.RunTaskMutator#updateJavaExecTask
can be patched to shorten the command line? I would propose to use "Solution 1" of gradle/gradle#10114 (comment).The text was updated successfully, but these errors were encountered: