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: 0.18.0 -> 0.20.0 #51783

Merged
merged 3 commits into from Dec 14, 2018
Merged

bazel: 0.18.0 -> 0.20.0 #51783

merged 3 commits into from Dec 14, 2018

Conversation

mboes
Copy link
Contributor

@mboes mboes commented Dec 9, 2018

This PR includes the removal of the bazel_jdk11 package, which is
now redundant with the bazel package.

…lCheckPhase.

This change is going to be required when upgrading to Bazel 0.20.0,
because in the checkPhase we're not wrapping the Bazel binary yet to
set some necessary default arguments.
This package is redundant, since Bazel (since the upgrade to v0.20.0),
now uses JDK 11 as the runtime JDK.
@@ -8259,10 +8259,6 @@ in
bazel = callPackage ../development/tools/build-managers/bazel {
inherit (darwin) cctools;
inherit (darwin.apple_sdk.frameworks) CoreFoundation CoreServices Foundation;
};
bazel_jdk11 = callPackage ../development/tools/build-managers/bazel {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There might not be a need for the runJdk parameter after this.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn’t it still be a useful distinction to have both runJdk and buildJdk, even if they are effectively the same?

@Profpatsch Profpatsch merged commit 8d8b443 into NixOS:master Dec 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants