| commit | 7c9f8fc8620e2d092e987e6aea07983492bdd214 | [log] [tgz] |
|---|---|---|
| author | Adam Gross <grossag@vmware.com> | Fri Aug 07 06:21:16 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Aug 07 06:22:32 2020 -0700 |
| tree | 7561088b3163c5b074ac8e38d09b41f4cc89f8cc | |
| parent | be25b25a62a0e0fc2139856c2a9e3d8f011438e8 [diff] |
Add useDefaultShellEnvironment() in two places within the Java rules Two files in the Java tools were not using useDefaultShellEnvironment() when using the SpawnAction.Builder class. This causes the PATH to be dropped when using these rules, even if the user passed --action_env=PATH. This is problematic for me because I depend on the PATH to help Bazel find the MSVCRT dlls. Closes #11889. PiperOrigin-RevId: 325424677
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
