Convert jshell-based scripts to plain java programs

Closes #578

Author: sormuras

.github/workflows/build-all-examples.yml

@@ -17,13 +17,13 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
-      - name: 'Set up JDK 21'
+      - name: 'Set up JDK 24'
         uses: actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00 # v4.7.1
         with:
-          java-version: 21
+          java-version: 24
           distribution: temurin
       - uses: sbt/setup-sbt@6c68d2fe8dfbc0a0534d70101baa2e0420e1a506 # v1.1.9
-      - name: 'Build all examples using JShell'
+      - name: 'Build all examples'
         run: java src/Builder.java
       - name: 'Check automation for updating versions'
         run: java src/Updater.java 42

.github/workflows/codeql.yml

@@ -25,10 +25,10 @@ jobs:
             build-mode: manual
     steps:
       - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
-      - name: 'Set up JDK 21'
+      - name: 'Set up JDK 24'
         uses: actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00 # v4.7.1
         with:
-          java-version: 21
+          java-version: 24
           distribution: temurin
       - uses: sbt/setup-sbt@6c68d2fe8dfbc0a0534d70101baa2e0420e1a506 # v1.1.9
       - name: Initialize CodeQL

README.md

@@ -3,8 +3,9 @@
 Welcome to _JUnit Examples_, a collection of example applications and extensions
 using JUnit Jupiter, JUnit Vintage, and the JUnit Platform on various build systems.
 
-CI builds for example projects are performed by [GitHub Actions][ci-actions]. Using JDK 11+'s
-`jshell` tool, you may build all examples via the `build-all-examples.jsh` script.
+CI builds for example projects are performed by [GitHub Actions][ci-actions]. Using JDK 24+'s
+`java` multi-file source-code launcher feature, you may build all examples by running
+`java src/Builder.java` in the main directory of this project.
 
 ## Jupiter Starter Examples
 

junit-modular-world/.gitignore

@@ -1,3 +1,4 @@
 bin/
 lib/
+!src/build/
 .jqwik-database

junit-modular-world/README.md

@@ -2,11 +2,11 @@
 
 The project layout structure and command line tools usages are based on proposals
 introduced by the [**Module System Quick-Start Guide**](https://openjdk.java.net/projects/jigsaw/quick-start).
-Invoke the [jshell](https://docs.oracle.com/javase/9/tools/jshell.htm) script
-`./build.jsh` (Windows: `jshell build.jsh`) to build this example project.
+Invoke [java](https://openjdk.org/jeps/458)'s source launcher
+`java src/build/Build.java` to build this example project.
 
-This example project does not aim to demonstrate how to use the JUnit Platform APIs.
-For detailed  information on the JUnit Platform programming and extension models,
+This example project does not aim to demonstrate how to use the JUnit Framework APIs.
+For detailed information on the JUnit Framework programming and extension models,
 please consult the [User Guide](https://docs.junit.org/current/user-guide/).
 
 ## Source Layout
@@ -22,7 +22,7 @@ It tests the exported packages and types of the main modules.
 
 ## Binary Layout
 
-Main binaries are compiled and packaged using `./compile.jsh`.
+Main binaries are compiled and packaged using `java src/build/Compile.java`.
 
 For example, here are the commands to compile and package the `com.example.tool` module.
 This and the `com.example.application` module don't need external module dependencies.
@@ -57,18 +57,16 @@ jar
     .
 ```
 
-Here is the partly expanded tree of the `bin/` directory after running `./compile.jsh`:
+Here is the partly expanded tree of the `bin/` directory after running `java src/build/Compile.java`:
 
 ![junit-modular-world/bin](doc/screenshot-bin.png)
 
 
 ## Running Tests
 
-Compiling and running tests is achieved by calling the following test scripts: 
+Compiling and running tests is achieved by calling the following Java program: 
 
-- `test-classpath.jsh`
-- `test-patch-compile.jsh`
-- `test-patch-runtime.jsh`
+- `java src/build/Build.java`
 
 ```
 ╷
@@ -116,7 +114,7 @@ Compiling and running tests is achieved by calling the following test scripts:
 ## Ice Cream Test Engine
 
 The `ice.cream` module demonstrates how to write and register your own `TestEngine`
-implementation using the Java Platform Module System.
+implementation using a Java module descriptor.
 This engine does not find any tests in containers, but _discovers_ a configurable
 amount of ice cream scoops.
 

junit-modular-world/build.jsh

@@ -0,0 +1,8 @@
+public class Build {
+  public static void main(String[] args) throws Exception {
+    var project = Project.ofCurrentWorkingDirectory();
+    project.clean();
+    project.compile();
+    project.test();
+  }
+}

junit-modular-world/compile.jsh

@@ -0,0 +1,5 @@
+public class Compile {
+  public static void main(String[] args) throws Exception {
+    Project.ofCurrentWorkingDirectory().compile();
+  }
+}