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
{{ message }}
This repository was archived by the owner on May 23, 2025. It is now read-only.
When the Java classpath is long, the command line "-cp" argument passed to groovyc exceeds the Linux maximum size for any single command argument, which is roughly 131K.
I have a hack to groovy/groovy.bzl that works around the problem by using symlinks. The groovyc command really needs a way to specify very long classpaths. Maybe it would be better to set the CLASSPATH environment variable in the Bazel rule?
When the Java classpath is long, the command line "-cp" argument passed to groovyc exceeds the Linux maximum size for any single command argument, which is roughly 131K.
I have a hack to groovy/groovy.bzl that works around the problem by using symlinks. The groovyc command really needs a way to specify very long classpaths. Maybe it would be better to set the CLASSPATH environment variable in the Bazel rule?
What do you think?