This repository has been archived by the owner on Jun 4, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 28
Bazel 0.19 Support #122
Comments
Wow, you're on top of it ;) Bazel 0.18 came out less than two weeks ago. |
Hah. I'm going to push hard to get the s3 pr merged because upgrading to HEAD every few months is less than ideal :D |
:) HTTP basic auth with lamda@edge or API gateway authenticator....it could happen. |
jjudd
pushed a commit
to lucidsoftware/rules_scala
that referenced
this issue
May 7, 2019
… warnings. The current code with more recent versions of Bazel causes a warning about using the deprecated target '@local_jdk//:java' and to use use @bazel_tools//tools/jdk:current_java_runtime instead (see bazelbuild/bazel#5594). Resolves higherkindness#122
jjudd
pushed a commit
to lucidsoftware/rules_scala
that referenced
this issue
May 8, 2019
… warnings. The current code with more recent versions of Bazel causes a warning about using the deprecated target '@local_jdk//:java' and to use use @bazel_tools//tools/jdk:current_java_runtime instead (see bazelbuild/bazel#5594). Resolves higherkindness#122
jjudd
pushed a commit
to lucidsoftware/rules_scala
that referenced
this issue
May 17, 2019
Includes updating the _java attribute to use current_java_runtime and get rid of warnings. The current code with more recent versions of Bazel causes a warning about using the deprecated target '@local_jdk//:java' and to use use @bazel_tools//tools/jdk:current_java_runtime instead (see bazelbuild/bazel#5594). Resolves higherkindness#122
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Annex warns on some things in 0.19. I'm working on fixing them, but using this issue to document the things I'm running into
...depends on deprecated target '@local_jdk//:java': Don't depend on targets in the JDK workspace; use @bazel_tools//tools/jdk:current_java_runtime instead (see https://github.com/bazelbuild/bazel/issues/5594).
The text was updated successfully, but these errors were encountered: