Make jdk dependency explicit

[jcoveney]

This should fix the issue that came up after the fact here

#36

@damienmg, thank you for pointing this out! A question to mull over with @johnynek: how can we avoid this?

Is there an issue if we set up the automatic CI to run on different architectures? Is it a cost concern?

Also, any word on sandboxing in OSX? I see this bazelbuild/bazel#902, but there's not code or anything.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[johnynek]

I think @damienmg may be able to set up bazel's CI that does not use Docker.

[damienmg]

This has fixed the build \o/

Yes I am working on making our CI vet every PR but it is not going fast because we need to scale it (and I am on rotation this week, which mean I have to ping everybody for breakage, you included :))

[damienmg]

@hermione521 is working on sandboxing for OS X currently, see https://bazel-review.googlesource.com/#/c/3383/