Introduce Cursor/VS Code support #655
Conversation
pan3793
left a comment
pan3793
left a comment
There was a problem hiding this comment.
Having never experienced VS Code for Scala/Java projects previously, I have successfully used VS Code to import the Spark project by following the instructions, and confirmed that basic functionalities like code jump work as expected.
| - *Confirm Build Server*: Metals defaults to using Bloop as the build server. Do not change this setting, as Bloop provides the fastest compilation and best integration for local development. Open the Command Palette (Cmd+Shift+P or Ctrl+Shift+P), run `Metals: Run doctor`, and verify the status dashboard. Ensure it shows: `Build definition is coming from sbt` and `Build server currently being used is Bloop`. | ||
|
|
||
| If you encounter compilation errors or the IDE fails to recognize symbols, follow these steps to perform a clean import: | ||
| 1. *Stop Bloop Server*: Run the following command in your terminal to stop the bloop server: `pkill -f "bloop.BloopServer"`. If you have installed bloop CLI you can run `bloop exit` instead. |
There was a problem hiding this comment.
Is this equivalent to Metals: Restart server?
There was a problem hiding this comment.
metals server is different from bloop server.
|
|
||
| If you encounter compilation errors or the IDE fails to recognize symbols, follow these steps to perform a clean import: | ||
| 1. *Stop Bloop Server*: Run the following command in your terminal to stop the bloop server: `pkill -f "bloop.BloopServer"`. If you have installed bloop CLI you can run `bloop exit` instead. | ||
| 2. *Clean Workspace*: Run the following command in your terminal to remove cached build metadata: `rm -rf .bloop/ .metals/ .bsp/`. |
There was a problem hiding this comment.
Do we need to rm ./project/.bloop too?
There was a problem hiding this comment.
I didn't remove it and there is no issue. I checked a bit and this .bloop is only for building the sbt build definition, which is simply the SparkBuild.scala. It's unlikely to cause issues.
3 participants
Cursor/VS Code is well supported now after apache/spark#53621 . This PR introduces the steps to use Cursor/VS Code.