removed dead eclipse references

Author: jurgenvinju

courses/GettingHelp/GettingHelp.md

@@ -30,7 +30,6 @@ details:
    3. The (open) issues registered with [Github Issues](http://github.com/usethesource/rascal/issues)
 * Directly in the Rascal IDE there is help available:
    1. On the commandline, type `:help`
-   2. In Eclipse there is the `Tutor View` which opens all the documentation pages inside Eclipse.
    3. In VScode use the command palette and search for `Rascal` for more commands.
 * For specific application topics, "Howto" kind of information, etc. please go to ((FurtherReading)).
 * There is a lot of documentation on Rascal and its libraries. Read the ((Browsing)) page on how to navigate it.

courses/GettingStarted/CreateNewProject/CreateNewProject.md

@@ -8,8 +8,7 @@ import IO;
 remove(|home:///my-project-name|, recursive=true);
 ```
 
-Rascal projects, generally, work the same in all three IDE contexts:
-* Eclipse
+Rascal projects, generally, work the same in all IDE contexts:
 * VScode
 * Commandline
 
@@ -22,9 +21,7 @@ import util::Reflective;
 newRascalProject(|home:///my-project-name|)
 ```
 
-The Eclipse plugin has a "New Project Wizard" you can use as well.
-
-The next step is to import the new project into VScode or Eclipse, or
+The next step is to import the new project into VScode, or
 to `cd` to the project's root directory. From there on ((RunningRascal))
 with the new project's source and library settings is trivial.
 
@@ -52,8 +49,7 @@ The `pom.xml` file is the basic setup that names the project and defines its dep
 ```
 
 Next to that `RASCAL.MF` is required to configure the development environment for the project. Some
-information from the `pom.xml` is repeated here, because this file is common between Eclipse, VScode and empty commandline projects,
-and such projects could work with a `pom.xml`:
+information from the `pom.xml` is repeated here, because this file is common between VScode and empty commandline projects, and such projects should work with a `pom.xml`:
 
 ```MF
 ((|home:///my-project-name/META-INF/RASCAL.MF|))
@@ -64,3 +60,11 @@ And finally in `src/main/rascal` you'll find the Rascal source files, as configu
 ```rascal
 ((|home:///my-project-name/src/main/rascal/Main.rsc|))
 ```
+
+#### Benefits
+
+* The ((newRascalProject)) sets up a project for use with the Rascal ((MavenPlugin)).
+
+#### Pitfalls
+
+* In `RASCAL.MF` the `Sources` configuration option will be replaced by pom.xml's `<srcs>` tag.

courses/GettingStarted/DownloadAndInstallation/DownloadAndInstallation.md

@@ -7,7 +7,6 @@ Rascal is deployed as one of four easy-to-use packages:
 
 1. **A standalone "jar" file**, which can be downloaded [here](https://update.rascal-mpl.org/console/rascal-shell-stable.jar)
 2. A **Visual Studio Code extension**, which can be found [here](https://marketplace.visualstudio.com/items?itemName=usethesource.rascalmpl) or search for "Rascal" in the "Extension" view in VScode itself.
-3. An **Eclipse plugin**, for which the update site is <https://update.rascal-mpl.org/stable/>.
-4. A set of **Maven MOJOs**, for which the plugin repository is <https://releases.usethesource.io/maven/>
+4. A ((MavenPlugin)) with a set of Rascal Mojo's, for which the plugin repository is <https://releases.usethesource.io/maven/>
 
 See ((RunningRascal)) for what to do next.

courses/GettingStarted/RunningRascal/Eclipse/Eclipse.md

@@ -7,7 +7,6 @@ sidebar_position: 2
 
 1. On the Unix or Windows [Commandline]((RunningRascal-Commandline)), start a ((RascalShell)) by: `java -jar rascal-<version>.jar`
 2. In [VScode]((RunningRascal-VScode)), in the command palette type `Rascal` and select `Create Rascal Terminal`
-3. In [Eclipse]((RunningRascal-Eclipse)), from the button bar select the button with the Rascal logo.
 4. With Maven, ((CreateNewProject)) first and then type: `mvn rascal:console`
 
 You will be prompted for input right after the version is printed and a lot of information about the current searchpath configuration. 

courses/GettingStarted/RunningRascal/Eclipse/eclipse-commandbutton-screenshot.png

@@ -28,9 +28,6 @@ This can be caused by
 Remedies:
 
 *  Correct the mispelled name.
-*  In Eclipse the safest way to execute a Rascal module is to select it in the Package Explorer, 
-right click on it and then select `Run as Rascal Application`.
-
 *  At the command line, change directory to where the toplevel module of your program is located and then execute the Rascal Shell.
 
 #### Examples

courses/GettingStarted/RunningRascal/Eclipse/eclipse-menu-screenshot.png

@@ -12,7 +12,7 @@ sidebar_position: 10
 
 ## Abstract
 
-Rascal can be executed in JVM threads (as in the Eclipse context for example) and also we plan to add concurrency features to Rascal itself ((RAP8)). This puts a lot more pressure on our IO mechanism than before, leading to races on disk and on other external resources identified by values of type `loc`.
+Rascal can be executed in JVM threads and also we plan to add concurrency features to Rascal itself ((RAP8)). This puts a lot more pressure on our IO mechanism than before, leading to races on disk and on other external resources identified by values of type `loc`.
 
 We propose to extend the URIResolverRegistry (which is Rascal’s generic resource access mechanism) with a cross-cutting “locking” feature that is safe (up to *unpredicted* aliasing of location URIs). 
 
@@ -21,7 +21,7 @@ A second part of the proposal is to expose this locking feature on the language
 ## Motivation
 
 * Many use cases of Rascal involve file IO  
-  * Often in a dynamic context where multiple file processors read and write concurrently, such as the Eclipse IDE or an LSP server.  
+  * Often in a dynamic context where multiple file processors read and write concurrently, such as the an LSP server.  
   * More and more in a concurrent and even parallel context, where multi-core architectures are used to speed up larger computations  
 * File IO is hazardous in a concurrent context, due to race conditions  
 * So, we need some form of locking mechanism on file IO.  

courses/GettingStarted/RunningRascal/RunningRascal.md

@@ -4,7 +4,7 @@ title: Measuring Java
 
 #### Synopsis
 
-A few steps using the M3 model to compute basic metrics for a Java project in Eclipse.
+A few steps using the M3 model to compute basic metrics for a Java project in VScode.
 
 #### Syntax
 
@@ -17,10 +17,10 @@ A few steps using the M3 model to compute basic metrics for a Java project in Ec
 #### Description
 
 
-This is a recipe for computing basic or more advanced metrics from a Java project in Eclipse. We assume:
+This is a recipe for computing basic or more advanced metrics from a Java project. We assume:
 
-* You have Rascal installed in an Eclipse instance.
-* You have a Java project in your Eclipse workspace that compiles without errors. Let's call it `HelloWorld`.
+* You have the Rascal extension installed in an VScode instance.
+* You have a Java project in your VScode workspace that compiles without errors. Let's call it `HelloWorld`.
 
 
 Now we will follow the [EASY]((EASY)) paradigm: