quick update on this: • jvm: use argfiles for JVM and JVM-compiler process arguments was updated in response to comments • jvm: fix ambiguous classpath provider for protobuf targets consumed by both Java and Scala codegen was closed and this issue was opened to discuss the design: Design doc: resolving codegen ambiguity when one generator target serves multiple consumer languages

Another little bump on this. We starting a migration of Scala build to Pants and solving these issues would make our life easier.

Since the design doc received no feedback, I implemented it in this PR: jvm: resolve protobuf codegen ambiguity per requesting language