Run arbitrary main in scala feature has been broken

[ittaiz]

Hi,
The ability to right click any main in a scala_library and run it has been broken recently. Unfortunately it wasn't recently enough so it was before the fine grain commits and we don't know which commit did it.
The current situation is that the run configuration is created with a correct before task (I see from the console the right _deploy jar is built) but then the run configuration is somehow configured incorrectly.
I'd love to contribute an e2e for this to cover future regression but not sure where to start.
@jin @brendandouglas would you accept an e2e for this feature? If so can you share a few pointers?

Thanks!

[liucijus]

This seems to fail finding artifact after this change:
98d0504#diff-c924e38cec968aa15f096048cb42b57fR185

[ittaiz]

@brendandouglas @jin @liucijus found that if we revert that one line the feature goes back to working. Would you be open to a PR reverting this?
We'd still love adding a test to protect from such a regression if you can point us towards where

[jin]

@ittaiz @liucijus can you provide a Scala repro example for this? For future issue reports, it will really help us if you can provide Scala repro projects as we don't really have expertise on the language.

[liucijus]

https://github.com/liucijus/bazel-scala-example can be used to reproduce the problem:
Import Bazel project, add scala view in project view then click on the green run arrow next to Main class in com.example.Main.
Expected: runs and prints "Hello!"
Actual: Red notification "Failed to find deployable jar when building //:mainlib"

[liucijus]

@jin, FYI, I had problems importing example project on custom build from master source: #1183

[liucijus]

Thanks, @jin!