-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
incompatible_use_remote_java_toolchain: use remote Java tools instead of the embedded deploy jars #7196
Comments
…t java_toolchain and host_java_toolchain. This PR introduces the flags: * `--incompatible_use_remote_host_java_toolchain` * `--incompatible_use_remote_java_toolchain` Progress on bazelbuild#6316 bazelbuild#7196 bazelbuild#7197 Closes bazelbuild#7156. PiperOrigin-RevId: 230209934
For this flag and the one in #7197 - what if users don't want to download this archive, or want to change the location/manner in which this archive is obtained? This would be important for CI systems with no internet connectivity, and orgs that want to audit/control build-time dependencies (both in terms of artifacts and systems). Will there be a flag moving forward that will disable this download? |
@scottmin0r To not download the archive you have to set the flags |
Specifically what should I pass for those flag values? As per this comment I've tried: (release 0.24.1)
but this still seems to try to download tools (with two different failure modes):
|
The option
--incompatible_use_remote_java_toolchain
will download the remote Java tools (archive of deploy jars) for the target configuration instead of using the corresponding embedded deploy jars. Enabling this flag only affects users of the Java rules.Migration Notes
There are no actions required from the users. No migration is needed.
The text was updated successfully, but these errors were encountered: