Remove std:// from Rascal-LSP path config.

Author: toinehartman

src/org/rascalmpl/library/util/PathConfig.java

@@ -493,28 +493,30 @@ private static void buildRascalSelfApplicationConfig(ISourceLocation workspaceRa
      * Configure paths for the rascal-lsp project when it's open in the IDE (the runtime inside rascal-lsp is not configured here)
      */
     private static void buildRascalLSPConfig(ISourceLocation manifestRoot, RascalConfigMode mode, List<Artifact> mavenClasspath, IListWriter srcs, IListWriter libs, IListWriter messages) throws IOException {
-        var insideRascalJar = JarURIResolver.jarify(resolveCurrentRascalRuntimeJar());
+        var currentRascalRuntimeJar = resolveCurrentRascalRuntimeJar();
+        var insideRascalJar = JarURIResolver.jarify(currentRascalRuntimeJar);
+        var rascalLibrary = URIUtil.getChildLocation(insideRascalJar, "org/rascalmpl/library");
         var rascalCompiler = URIUtil.getChildLocation(insideRascalJar, "org/rascalmpl/compiler");
         var typepal = URIUtil.getChildLocation(insideRascalJar, "org/rascalmpl/typepal");
 
         if (mode == RascalConfigMode.INTERPRETER) {
-            // we're building a repl for the rascal-lsp project
+            // we're building a REPL for the rascal-lsp project
             // so this is a rascal-lsp developer working on code in rascal-lsp
             // most stuff flows from the
-            srcs.append(URIUtil.rootLocation("std"));
+            srcs.append(rascalLibrary);
             srcs.append(rascalCompiler);
             srcs.append(typepal);
         }
         else {
-            libs.append(JarURIResolver.jarify(resolveCurrentRascalRuntimeJar()));
+            libs.append(insideRascalJar);
             // while it's tempting to see if the rascal project is there, and we might be able to get the rascal compiler tpls from the target folder.
             // as long as we're hard wiring the rascal compler to follow the runtime
             // we have to let the type-checker for rascal-lsp re-type-check rascal compiler
             // this allows developers in rascal-lsp to get typechecking for parts even if they import rascal compiler/typepal modules
             srcs.append(rascalCompiler);
             srcs.append(typepal);
         }
-        libs.append(resolveCurrentRascalRuntimeJar()); // add our own jar to the lib path to make sure rascal classes are found
+        libs.append(currentRascalRuntimeJar); // add our own jar to the lib path to make sure rascal classes are found
 
         translateSources(manifestRoot, srcs, messages);