You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/howtos/development/build-spoofax.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ The `-s` flag build Stratego/XT instead of downloading it, and `-t` skips the St
93
93
Use `.\bd.bat build` to get a list of components available for building, and `.\bd.bat build --help` for help on all the command-line flags and switches.
94
94
95
95
!!! warning ""
96
-
If you have opened a project in the repository in Eclipse, you **must turn off**_Project_ ‣ _Build Automatically_in Eclipse, otherwise the Maven and Eclipse compilers will interfere and possibly fail the build. After the Maven build is finished, enable _Build Automatically_ again.
96
+
If you have opened a project in the repository in Eclipse, you **must turn off**`#!gui Project > Build Automatically`in Eclipse, otherwise the Maven and Eclipse compilers will interfere and possibly fail the build. After the Maven build is finished, enable `#!gui Build Automatically` again.
97
97
98
98
99
99
## Updating the Source Code
@@ -180,4 +180,4 @@ If updating or checking out a branch of submodule fails (because of unstaged or
180
180
Resetting and cleaning **deletes uncommitted and unpushed changes**, which can cause **permanent data loss**. Make sure all your changes are committed _and_ pushed!
181
181
182
182
### Weird Compilation Errors
183
-
If you get any weird compilation errors during the command-line build, make sure that _Project_ ‣ _Build Automatically_ is turned off in Eclipse.
183
+
If you get any weird compilation errors during the command-line build, make sure that `#!gui Project > Build Automatically` is turned off in Eclipse.
Copy file name to clipboardExpand all lines: content/howtos/development/develop-spoofax.md
+11-11Lines changed: 11 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -38,26 +38,26 @@ This will download and install Eclipse into `~/eclipse/spoofax-dev` with the rig
38
38
### Fixing Eclipse Settings
39
39
Some Eclipse settings unfortunately have sub-optimal defaults. Go to the Eclipse preferences and set these options:
40
40
41
-
- General
41
+
-`#!gui General`
42
42
-**Enable**: Keep next/previous editor, view and perspectives dialog open
43
-
- General ‣ Startup and Shutdown
43
+
-`#!gui General > Startup and Shutdown`
44
44
-**Enable**: Refresh workspace on startup
45
-
- General ‣ Workspace
45
+
-`#!gui General > Workspace`
46
46
-**Enable**: Refresh using native hooks or polling
47
-
- Maven
47
+
-`#!gui Maven`
48
48
-**Enable**: Do not automatically update dependencies from remote repositories
49
49
-**Enable**: Download Artifact Sources
50
50
-**Enable**: Download Artifact JavaDoc
51
-
- Maven ‣ Annotation Processing
51
+
-`#!gui Maven > Annotation Processing`
52
52
-**Enable**: Automatically configure JDT APT
53
-
- Maven ‣ User Interface
53
+
-`#!gui Maven > User Interface`
54
54
-**Enable**: Open XML page in the POM editor by default
55
-
- Run/Debug ‣ Launching
55
+
-`#!gui Run/Debug > Launching`
56
56
-**Disable**: Build (if required) before launching
57
57
58
58
59
59
### Developing
60
-
Import the projects you’d like to develop. To import Java and language projects, use _Import ‣ Maven ‣ Existing Maven Projects_. Eclipse plugins are still imported with _Import ‣ General ‣ Existing Projects into Workspace_.
60
+
Import the projects you’d like to develop. To import Java and language projects, use `#!gui Import > Maven > Existing Maven Projects`. Eclipse plugins are still imported with `#!gui Import > General > Existing Projects into Workspace`.
61
61
62
62
63
63
### Running
@@ -70,13 +70,13 @@ Some tricks:
70
70
71
71
72
72
### Troubleshooting
73
-
If launching the guest Eclipse does not work due to a missing JavaSE-11, you need to register a Java 11 compatible JRE. Go to _Preferences_ ‣ _Java_ ‣ _Installed JREs_, and click the Add... button, and find the install directory of your Java 11 compatible JRE. For example, when you've installed Java 11 with SDKMAN, it may be at `~/.sdkman/candidates/java/11.0.13-tem`.
73
+
If launching the guest Eclipse does not work due to a missing JavaSE-11, you need to register a Java 11 compatible JRE. Go to `#!gui Preferences > Java > Installed JREs`, and click the `#!gui Add...` button, and find the install directory of your Java 11 compatible JRE. For example, when you've installed Java 11 with SDKMAN, it may be at `~/.sdkman/candidates/java/11.0.13-tem`.
74
74
75
-
If there are many errors in a project, try updating the Maven project. Right click the project and choose _Maven_ ‣ _Update Project..._, uncheck _Clean projects_in the new dialog and press _OK_. This will update the project from the POM file, update any dependencies, and trigger a build. If this does not solve the problems, try it again but this time with _Clean projects_ checked. Note that if you clean a language project, it has to be rebuilt from the command-line. Restarting Eclipse and repeating these steps may also help.
75
+
If there are many errors in a project, try updating the Maven project. Right click the project and choose `#!gui Maven > Update Project...`, uncheck `#!gui Clean projects`in the new dialog and press `#!gui OK`. This will update the project from the POM file, update any dependencies, and trigger a build. If this does not solve the problems, try it again but this time with `#!gui Clean projects` checked. Note that if you clean a language project, it has to be rebuilt from the command-line. Restarting Eclipse and repeating these steps may also help.
76
76
77
77
Multiple projects can be updated by selecting multiple projects in the package/project explorer, or by checking projects in the update dialog.
78
78
79
-
If you have particular trouble with `org.eclipse.*` plugins in the `MANIFEST.MF` file that do not resolve, try the following. Go to _Preferences_ ‣ _Plug-in Development_ ‣ _Target Platform_, most likely there will not be an active _Running Platform_ there. You can use _Add..._ to add a new one if there isn’t one already. Select the _Default_ option, click _Next_, then click _Finish_. Check the box next to the platform to activate it.
79
+
If you have particular trouble with `org.eclipse.*` plugins in the `MANIFEST.MF` file that do not resolve, try the following. Go to `#!gui Preferences > Plug-in Development > Target Platform`, most likely there will not be an active _Running Platform_ there. You can use `#!gui Add...` to add a new one if there isn’t one already. Select the _Default_ option, click `#!gui Next`, then click `#!gui Finish`. Check the box next to the platform to activate it.
Copy file name to clipboardExpand all lines: content/howtos/development/troubleshooting.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -109,7 +109,7 @@ The path /var/folders/a_/foo0000bar/T/vfs_cache-345/tmp_123_macosx/sdf2table-mac
109
109
is not shared from the host and is not known to Docker.
110
110
```
111
111
112
-
Ensure the root of the path (`/var/folders` in this example) is shared in Docker for Mac. Go to Docker for Mac _Preferences_ ‣ _Resources_ ‣ _File Sharing_ and add the path to the list. The default list should contain:
112
+
Ensure the root of the path (`/var/folders` in this example) is shared in Docker for Mac. Go to Docker for Mac `#!gui Preferences > Resources > File Sharing` and add the path to the list. The default list should contain:
113
113
114
114
-`/Users`
115
115
-`/Volumes`
@@ -125,4 +125,4 @@ bind source path does not exist:
Ensure that both Docker and the terminal from which you are invoking the build have _full-disk access_. Go to macOS _Preferences_ ‣ _Security and Privacy_ ‣ _Full Disk Access_ and check the checkboxes next to _Docker_ and your terminal (_Terminal_ and/or _iTerm_).
128
+
Ensure that both Docker and the terminal from which you are invoking the build have _full-disk access_. Go to macOS `#!gui Preferences > Security and Privacy > Full Disk Access` and check the checkboxes next to _Docker_ and your terminal (_Terminal_ and/or _iTerm_).
0 commit comments