'No such file or directory' on Windows

[majcherm-da]

rules_scala doesn't work properly on Windows.

This can be reproduced by building:

bazel test //test:HelloLibTest

on rules_scala itself (test folder).

After switching to a commit before: https://github.com/bazelbuild/rules_scala/pull/568/files/bd8ff42e35d8f8bb0181aea5cf0439512c6df32e
which introduced another issue (reported here: #642), this is what I'm getting:

It tries to lookup a JAVABIN wrapper in <name>.runfiles folder, but this one is almost empty on Windows.

(Similar thing happens for rules_java - this folder is also almost empty, but in case of java a different laucher is used for which this doesn't cause a problem:
https://github.com/bazelbuild/bazel/blob/556839466dd49958a6b058a3a4c2ad341c8d06f1/src/main/java/com/google/devtools/build/lib/bazel/rules/java/BazelJavaSemantics.java#L380)

Wrapper script is properly generated, but it resides in the same location as runfiles directory only. On unix boxes the file is present in both locations and thus it works.

[ittaiz]

I don’t understand, what is rules_java? Is this in bazel-core? If so are you saying bazel itself doesn’t work on windows?

…

On Mon, 19 Nov 2018 at 18:42 Michał Majcherski ***@***.***> wrote: rules_scala doesn't work properly on Windows. This can be reproduced by building: bazel test //test:HelloLibTest on rules_scala itself (test folder). After switching to a commit before: https://github.com/bazelbuild/rules_scala/pull/568/files/bd8ff42e35d8f8bb0181aea5cf0439512c6df32e which introduced another issue, this is what I'm getting: [image: scala_rules_runfiles] <https://user-images.githubusercontent.com/43614029/48721186-a91b1380-ec21-11e8-978b-9238918ae85d.PNG> It tries to lookup a JAVABIN wrapper in <name>.runfiles folder, but this one is almost empty on Windows. (Similar thing happens for rules_java - this folder is also almost empty, but in case of java a different laucher is used for which this doesn't cause a problem: https://github.com/bazelbuild/bazel/blob/556839466dd49958a6b058a3a4c2ad341c8d06f1/src/main/java/com/google/devtools/build/lib/bazel/rules/java/BazelJavaSemantics.java#L380 ) Wrapper script is properly generated, but it resides in the same location as runfiles directory only. On unix boxes the file is present in both locations and thus it works. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#641>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABUIF-3jTxJZeof_ir155A2yCg311kTGks5uwt-EgaJpZM4YpfF9> .

[majcherm-da]

By rules_java I meant: https://docs.bazel.build/versions/master/be/java.html. I've seen that rules_scala is based on it and I've also noticed similarities in artifacts which are getting produced for java and scala on different OSes. By this I meen that on OSX <name>.runfiles folder is fully populated with jdk, built jars, wrappers, etc. This happens for both java and scala. On Windows the runfiles folder is almost empty and it's like this for both java and scala, altough Bazel's Java rules work correctly on Windows). In java rules (from bazel) launcher is dfferent on Windows than on other OSes, which does not seem to be the case for rules_scala. rules_scala is trying to access files from <name>.runfiles folder, which is not populated on Windows.

I could paste several screenshot showing what's happening, but probably the easiest way to understand what's happening is running it on Windows. This can be very easily reproduced by following the steps from above.

[majcherm-da]

I created a PR to fix this problem. In short, use exe launcher instead of bash script on Windows: #717