Question: Pinned Bazel Version about rules_scala HOT 8 CLOSED

Yup, pretty simple. That's what #221 does.

from rules_scala.

@borkaehw do you know more about this?

from rules_scala.

It looks like it's not configurable at this moment. What is the use case that you will need to change it?

from rules_scala.

I'd like to use the latest Bazel version orthogonal to the version this library sets it to, currently the latest Bazel version is 0.28.0

from rules_scala.

You may be confusing something because there is no difference in this file between 0.27.0 and 0.28.0. There was a nice performance fix in the latest release though.

from rules_scala.

yeah, my original question was whether as a consumer of higherkindness/rules_scala, do we have to use the same version specified in this file (i.e. 0.27.0)? Or is it expected that things will work fine if the versions do not align? (Sorry still new to Bazel et al).

from rules_scala.

Ah yeah, the 0.27.0 here is just for this one script template. It theoretically could have a version incompatibility, but I haven't seen one yet, as it doesn't change very often.

from rules_scala.

Cool, so I guess my next question, without actually knowing how things work, would it be reasonable to make this configurable when the user calls scala_repositories?

The alternative might be maintaining a list of Bazel versions which work with specific higherkindness/rules_scala versions.

from rules_scala.