tree 011af67869e0e073db22655e806ec8686ac82360
parent 8ed7196aee2f312f131df58ea69f9d2b443d3f6a
author Laszlo Csomor <laszlocsomor@google.com> 1550130738 -0800
committer Copybara-Service <copybara-piper@google.com> 1550130829 -0800

Windows, launcher: separate jvm_flags by TAB

When Bazel embeds the jvm_flags data into the
java_binary launcher, it will now join the flags
on TAB instead of on space.

While TAB is just as much a legal character in
flags as space is, it is probably rarer, and as
such it's a slightly safer choice than joining the
flags on space (and thus losing the ability to
support flags with spaces in them).

This is a follow-up to https://github.com/bazelbuild/bazel/pull/7411

Next steps:

- Update Bazel to Bash-tokenize the jvm_flags
  before embedding them in the launcher. This is
  required because the jvm_flags attribute should
  support Bash-tokenization (according to the
  Build Encyclopedia).

- Update the launcher to escape the jvm_flags with
  WindowsEscapeArg2 instead of WindowsEscapeArg.

See https://github.com/bazelbuild/bazel/issues/7072

Closes #7421.

PiperOrigin-RevId: 233900484