Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CommandBuilder: remove useShell and setWorkingDir #5007

Closed

Conversation

laszlocsomor
Copy link
Contributor

@laszlocsomor laszlocsomor commented Apr 12, 2018

Remove the .useShell method, expect callers to
just pass the shell interpreter if they need it.
This removes the argument vector transformation
heuristic, and stops shelling out to cmd.exe on
Windows.

Also remove the .setWorkingDir method because
callers always had to set the working directory.
Instead, the CommandBuilder constructor takes the
working directory.

Closes #2190. (Test code still shells out to
cmd.exe though.)

Remove the .useShell method, expect callers to
just pass the shell interpreter if they need it.
This removes the argument vector transformation
heuristic, and stops shelling out to cmd.exe on
Windows. See bazelbuild#2190

Also remove the .setWorkingDir method because
callers always had to set the working directory.
Instead, the CommandBuilder constructor takes the
working directory.

Change-Id: I545e01c811daaf34913cb585492923da81aa02ee
Change-Id: I7a694c9761e202e31352e69711e0c596dc51f905
Change-Id: I09dc604a0c5d53dc864e836ddc091b81aae590a2
@bazel-io bazel-io closed this in 073ea09 Apr 12, 2018
bazel-io pushed a commit that referenced this pull request Apr 16, 2018
It breaks downstream rules_nodejs. See #5028 for details.

RELNOTES: None.
PiperOrigin-RevId: 193074798
@laszlocsomor laszlocsomor deleted the cmdbuilder-useshell branch April 20, 2018 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants