cloud-fan commented on code in PR #655:
URL: https://github.com/apache/spark-website/pull/655#discussion_r2649659151


##########
site/developer-tools.html:
##########
@@ -606,6 +606,28 @@ <h5>Trigger the remote debugging</h5>
 <p>To exit remote debug mode (so that you don&#8217;t have to keep starting 
the remote debugger),
 type &#8220;session clear&#8221; in SBT console while you&#8217;re in a 
project.</p>
 
+<h4>Cursor/VS Code</h4>
+
+<p>You can leverage the power of <em>Cursor</em> or <em>VS Code</em> for Spark 
development by using the Metals extension. 
+Metals provides robust Scala support through the Build Server Protocol 
(BSP).</p>
+
+<p>Initial setup:</p>
+<ul>
+  <li><em>Install Metals</em>: Search for and install the Scala (Metals) 
extension from the Marketplace.</li>
+  <li><em>Open Project</em>: Open your Spark root directory.</li>
+  <li><em>Select Build Tool</em>: When prompted by the popup in the 
bottom-left corner, select sbt to read build definition.</li>
+  <li><em>Confirm Build Server</em>: 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 <code class="language-plaintext 
highlighter-rouge">Metals: Run doctor</code>, and verify the status dashboard. 
Ensure it shows: <code class="language-plaintext highlighter-rouge">Build 
definition is coming from sbt</code> and <code class="language-plaintext 
highlighter-rouge">Build server currently being used is Bloop</code>.</li>
+</ul>
+
+<p>If you encounter compilation errors or the IDE fails to recognize symbols, 
follow these steps to perform a clean import:</p>
+<ol>
+  <li><em>Clean Workspace</em>: Run the following command in your terminal to 
remove cached build metadata: <code class="language-plaintext 
highlighter-rouge">rm -rf .bloop/ .metals/ .bsp/</code>.</li>

Review Comment:
   ```suggestion
     <li><em>Stop Bloop Server</em>: Run the following command in your terminal 
to stop the bloop server: <code class="language-plaintext 
highlighter-rouge">pkill -f "bloop.BloopServer"</code>. If you have installed 
bloop CLI you can run <code class="language-plaintext highlighter-rouge">bloop 
exit</code> instead.</li>
     <li><em>Clean Workspace</em>: Run the following command in your terminal 
to remove cached build metadata: <code class="language-plaintext 
highlighter-rouge">rm -rf .bloop/ .metals/ .bsp/</code>.</li>
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to