You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
despite that, on bazel 0.2.3, we don't get an error with a missing main_class attribute (which leads to confusing error messages when the manifest is incorrect and we try to run.
The text was updated successfully, but these errors were encountered:
dslomov
added
P1
I'll work on this now. (Assignee required)
and removed
P2
We'll consider working on this in future. (Assignee optional)
labels
Dec 20, 2016
I'm unable to reproduce using a toy example under either a recent version (0.4.0) or 0.2.3.
Looking at the line you linked, if you're talking about the scala_library rule, it doesn't have the mandatory flag on "main_class" (line 531), only scala_binary does. (I don't know Scala but I assume it's expected that a library wouldn't need a main class.) If you're having an issue with another rule where the mandatory flag isn't being respected, please reopen and provide an example failure. Thanks!
in the scala rules we have:
https://github.com/bazelbuild/rules_scala/blob/master/scala/scala.bzl#L410
despite that, on bazel 0.2.3, we don't get an error with a missing
main_class
attribute (which leads to confusing error messages when the manifest is incorrect and we try to run.The text was updated successfully, but these errors were encountered: