-
-
Notifications
You must be signed in to change notification settings - Fork 286
How to make rules_scala use scala-2.10? #173
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
Comments
Thanks for the reply. And yes, I am interested in it. |
if you look in scala.bzl, we need to remove all references to Once we do that, you can change the bindings of those names to the 2.10 jars, and it should just work. See: https://github.com/bazelbuild/rules_scala/blob/master/scala/scala.bzl#L750 for repositories and then just remove all references to |
Thanks for the guide! According to your guide, I try to implement it. Here is the code:
Any suggestions? |
After reading the code, there's one thing confusing me. Why do we need to compile a scalac in |
The recompiled scalac is basically wrapping it in the bazel worker
infrastructure. This makes a temporary compile server that bazel will send
jobs to and is great for scalac (and javac) since they benefit highly from
a warmed JVM (and associated JITing).
…On Apr 2, 2017 7:56 AM, "Lin Min" ***@***.***> wrote:
After reading the code, there's one thing confusing me. Why do we need to
compile a scalac in src/java/io/bazel/rulesscale/scalac when there is
already a bin/scalac?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#173 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA9_-OrwNp3sN2fai7X1V9InBkTHCYRJks5rr7csgaJpZM4MrRvv>
.
|
Actually I have found that, maybe the error above is just because my code uses the 2.10 jars but still invokes the scalac which is compiled on scala-2.11 in
|
Closing since rules_scala does not support 2.10 anymore |
Hi! How to make rules_scala use scala-2.10? Does it need a hacky workaround?
The text was updated successfully, but these errors were encountered: