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

Bazel's embedded JDK is only used to run Bazel. #6313

Closed
meisterT opened this issue Oct 5, 2018 · 0 comments
Closed

Bazel's embedded JDK is only used to run Bazel. #6313

meisterT opened this issue Oct 5, 2018 · 0 comments
Assignees
Labels
P1 I'll work on this now. (Assignee required) team-Performance Issues for Performance teams

Comments

@meisterT
Copy link
Member

meisterT commented Oct 5, 2018

Currently we expose the embedded JDK as remote repository and also use it as host_javabase by default.

Design doc: https://docs.google.com/document/d/11OGJ2QTjnZgxbkgVFrKa3eD2DQ68qnXws7UQ1czc-qQ/edit#heading=h.5dewu068k9gb

See also #6216

@meisterT meisterT added this to the shrinking the bazel binary milestone Oct 5, 2018
@meisterT meisterT self-assigned this Oct 5, 2018
@jin jin added team-Performance Issues for Performance teams untriaged labels Oct 6, 2018
@meisterT meisterT added P1 I'll work on this now. (Assignee required) and removed untriaged labels Nov 29, 2018
bazel-io pushed a commit that referenced this issue Nov 30, 2018
Now we always use the remote JDK if host javabase is not explicitly set (and if
we need a JDK at all).

Progress on #6656 and #6592 and #6313.

RELNOTES: None
PiperOrigin-RevId: 223524214
bazel-io pushed a commit that referenced this issue Dec 6, 2018
Closes #6830.

Work towards #6313.

PiperOrigin-RevId: 224295602
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 I'll work on this now. (Assignee required) team-Performance Issues for Performance teams
Projects
None yet
Development

No branches or pull requests

2 participants