Convert to Maven focused starter project

Author: mpkorstanje

.github/workflows/build.yml

@@ -0,0 +1,30 @@
+name: Test Java
+
+permissions: { }
+
+on:
+  pull_request:
+    branches:
+      - main
+  push:
+    branches:
+      - main
+      - renovate/**
+
+jobs:
+  build:
+    strategy:
+      matrix:
+        os: [ ubuntu-latest, windows-latest ]
+        version: [ 17, 21 ]
+    name: 'Build Java ${{ matrix.version }} - ${{ matrix.os }}'
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-java@v5
+        with:
+          distribution: 'temurin'
+          java-version: ${{ matrix.version }}
+          cache: 'maven'
+      - name: Install dependencies
+        run: ./mvnw test

.github/workflows/test-java.yml

@@ -5,4 +5,8 @@
 # Eclipse IDE
 .settings
 .classpath
-.project
+.project
+
+# Maven
+target/
+*.versionsBackup

.gitignore

@@ -1,11 +1,8 @@
-# Cucumber-Java Skeleton
+# Cucumber JVM - Starter: Java with Maven
 
-This is the simplest possible setup for Cucumber using Java. There is nothing
-fancy like a webapp or browser testing. All this does is to show you how to
-set up and run Cucumber!
-
-There is a single feature file with one scenario. The scenario has three steps,
-two of them pending. See if you can make them all pass!
+This is the simplest possible setup for Cucumber-JVM using Java with Maven.
+There is nothing fancy like a webapp or browser testing. All this does is to
+show you how to set up and run Cucumber!
 
 To write assertions the project comes with [AssertJ](https://assertj.github.io/doc/#assertj-core-assertions-guide)
 included. 
@@ -25,26 +22,14 @@ Subversion:
 Or [download a zip](https://github.com/cucumber/cucumber-java-skeleton/archive/main.zip) file.
 
 ## Run the tests
-### Use Maven
 
 Open a command window and run:
 
-    cd maven
     ./mvnw test
 
 This runs Cucumber features using Cucumber's JUnit Platform Engine. The `Suite`
 annotation on the `RunCucumberTest` class tells JUnit to kick off Cucumber.
 
-### Use Gradle
-
-Open a command window and run:
-
-    cd gradle
-    ./gradlew test --rerun-tasks --info
-
-This runs Cucumber features using Cucumber's JUnit Platform Engine. The `Suite`
-annotation on the `RunCucumberTest` class tells JUnit to kick off Cucumber.
-
 ## Configuration 
 
 The [Cucumber JUnit Platform Engine](https://github.com/cucumber/cucumber-jvm/tree/main/cucumber-junit-platform-engine) uses configuration parameters to know what features to run,
@@ -80,7 +65,7 @@ Then add an annotation to `RunCucumberTest`.
 @IncludeTags("Zucchini")
 ```
 
-When using Maven, tags can be selected from the CLI using the `groups` and `excludedGroups` parameters. These take a
+Tags can be selected from the CLI using the `groups` and `excludedGroups` parameters. These take a
 [JUnit5 Tag Expression](https://junit.org/junit5/docs/current/user-guide/#running-tests-tag-expressions). 
 Note: When using JUnit, the `@` is not part of the tag.
 
@@ -95,16 +80,10 @@ with JUnit selectors. As a work around the `cucumber.features` property can be
 used. Because this property will cause Cucumber to ignore any other selectors
 from JUnit it is prudent to only execute the Cucumber engine.
 
-#### With Maven
-
 To select the scenario on line 3 of the `belly.feature` file use:
 
 ```
 ./mvnw test -Dsurefire.includeJUnit5Engines=cucumber -Dcucumber.features=src/test/resources/io/cucumber/skeleton/belly.feature:3 
 ```
 
 Note: Add `-Dcucumber.plugin=pretty` to get a more detailed output during test execution.
-
-#### With Gradle
-
-TODO: (I don't know how to do this. Feel free to send a pull request. ;))