@@ -22,26 +22,34 @@ sbt:scala3> projects
22
22
...
23
23
```
24
24
25
- These duplicated projects can be confusing and cause issues in IDEs.
25
+ These duplicated projects can be confusing and cause issues in IDEs, so it's
26
+ import to import the project in a specific way depending on your editor.
26
27
27
28
### Metals
28
29
29
30
When using Metals, the ` -bootstrapped ` projects are not exported by default.
30
31
Normally this is fine, but if you're working on certain modules like ` scaladoc `
31
32
you'll actually want these modules exported. In order to achieve this you'll
32
- first want to ensure you're using ` sbt ` as your build server instead of the
33
- default Bloop. You can achieve this with the ` Metals: Switch Build Server `
34
- command and then choosing sbt. Once you do this, you 'll want to find and change
35
- the following under ` commonBootstrappedSettings ` which is found in the
36
- [ ` Build.scala ` ] ( https://github.com/lampepfl/dotty/blob/main/project/Build.scala )
37
- file.
33
+ want to make sure you do two things:
34
+
35
+ 1 . You 'll want to find and change the following under
36
+ ` commonBootstrappedSettings ` which is found in the
37
+ [ ` Build.scala ` ] ( https://github.com/lampepfl/dotty/blob/main/project/Build.scala )
38
+ file.
38
39
39
40
``` diff
40
41
41
42
- bspEnabled := false,
42
43
+ bspEnabled := true,
43
44
```
44
45
46
+ 2 . Set ` sbt ` as your build server instead of the default, Bloop. You can achieve
47
+ this with the ` Metals: Switch Build Server ` command and then choosing sbt. In
48
+ VSCode, this looks like this:
49
+
50
+ ![ bsp-switch] ( https://user-images.githubusercontent.com/777748/241986423-0724ae74-0ebd-42ef-a1b7-4d17678992b4.png )
51
+
52
+
45
53
### IntelliJ
46
54
47
55
In IntelliJ IDEA, we recommend importing the dotty codebase through BSP, then
0 commit comments