re-enabled the tutor inside the rascal project locally. This only wor…

…ks because the standard library that the tutor uses itself is the same code as now being analyzed (and run) by the tutor. If you add a new builtin, for example, to Prelude, then this breaks again and you have to through a bootstrap cycle with rascal-tutor and rascal-maven-plugin before you can re-enable the tutor build here.

pom.xml

@@ -32,7 +32,7 @@
         <exec.mainClass>org.rascalmpl.shell.RascalShell</exec.mainClass>
         <rascal.test.memory>2</rascal.test.memory>
         <maven.compiler.release>11</maven.compiler.release>
-        <rascal-maven.version>0.22.0-RC2</rascal-maven.version>
+        <rascal-maven.version>0.25.0-RC2-SNAPSHOT</rascal-maven.version>
     </properties>
 
 
@@ -155,7 +155,7 @@
                             <goal>package</goal>
                         </goals>
                     </execution>
-                    <!--<execution> somehow this breaks if you add new builtins 
+                    <execution>
                         <id>default-cli</id>
                         <phase>compile</phase>
                         <goals>
@@ -176,7 +176,7 @@
                                 <ignore>${project.basedir}/src/org/rascalmpl/library/lang/rascal</ignore>
                             </ignores>
                         </configuration>
-                    </execution> -->
+                    </execution> 
                 </executions>
             </plugin>
             <plugin>