-
Notifications
You must be signed in to change notification settings - Fork 5
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
Bazel BSP support #420
Comments
Thanks for letting us know. That's quite unfortunate since we were piggybacking on the fact they decided to use BSP. I think it might be worth to help out with https://github.com/ValdemarGr/mezel instead which is written in Scala. The JetBrains codebase is in Kotlin, so less know to Scala developers and also quite big to continue supporting by us 🤔 On the other hand Mezel is one person project, so might be less mature overall. I certainly need to think about this. |
Yeah. Let me know where you land on this.I just got a monorepo working nicely with metals through the old 2024 release of bazel-bsp that metals has pinned, so definitely a bummer. As part of that, I did some poking in the Basel-bsp internals and would be probably able to help get it into a standalone state again if needed (maybe even port to scala?)The alternative definitely seems good - I need to try it out though. For my use case, slower and simpler is better than faster but more likely to crash. That said, maintained is better than unmaintained :)
…Sent from my iPhone
|
I was in the process of migrating a Scala Bazel codebase to use
bazel-bsp
and accidentally stumbled on the fact that it seems that JetBrains is planning on completely discontinuing that project JetBrains/hirschgarten#223!Any chance something could be forked under
scalameta
? The parts that matter to Metals could use some love, but are also relatively simple.bazel
I'm not sure if there are active consumers for the non Java/Scala parts - if that helps, we could consider taking those out.
The text was updated successfully, but these errors were encountered: