Replace incorrect Makefile CI steps with Gradle build workflow

[Copilot]

The failing build job was running a Makefile/autotools template (./configure, make) in a Gradle-based repository, causing an immediate hard failure. This updates the workflow to run the project’s actual Java/Gradle build path.

• Workflow alignment with repository build system

  • Renamed workflow from Makefile CI to Gradle CI.
  • Removed ./configure, make, make check, and make distcheck steps.
  • Added Java toolchain setup and replaced execution with a single Gradle build command.

• Runtime/toolchain configuration

  • Added actions/setup-java@v4 with Temurin JDK 21.
  • Kept build invocation minimal and deterministic via gradle build --no-daemon.

- name: Set up JDK 21
  uses: actions/setup-java@v4
  with:
    distribution: temurin
    java-version: "21"

- name: Build with Gradle
  run: gradle build --no-daemon

[Timonso-1]

es soll Java 25 verwendet werden

[Timonso-1]

@copilot Kann man machen das der sobald neuer psuh bzw. pr merge der ein neuen release erstellt?

[Copilot]

Pull request overview

Updates the GitHub Actions workflow to run the repository’s Gradle-based build instead of a Makefile/autotools template, addressing CI failures caused by incorrect build steps.

Changes:

• Renames the workflow to Gradle CI.
• Replaces ./configure / make / make check / make distcheck with Java setup and a Gradle build invocation.
• Adds actions/setup-java@v4 and enables Gradle caching.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.