Install

mutastic itself runs on JDK 25. The project it tests can be on JDK 17 or later: its tests run on the JDK its build gives them, as they always do.

Gradle

Until the Gradle Plugin Portal lists it, add Maven Central to where Gradle finds plugins, in settings.gradle.kts:

pluginManagement {
    repositories {
        mavenCentral()
        gradlePluginPortal()
    }
}

Then apply it in build.gradle.kts. The project’s own repositories need Maven Central too, for the mutastic command the tasks run:

plugins {
  id("io.mutastic") version "0.3.0"
}

repositories {
  mavenCentral()
}

./gradlew mutasticRun

mutastic runs on a JDK 25 Gradle toolchain, which Gradle finds or downloads.

Maven

Declare the plugin in your POM’s build plugins, so its goals take the short mutastic: prefix:

<plugin>
<groupId>io.mutastic</groupId>
<artifactId>mutastic-maven-plugin</artifactId>
<version>0.3.0</version>
</plugin>

mvn mutastic:run

Maven can run on JDK 17. mutastic finds a JDK 25 for itself: a JDK 25 toolchain in ~/.m2/toolchains.xml, else the JDK Maven runs on if it’s new enough, else the one -Dmutastic.jdk=<directory> names.

Command line

Download mutastic-0.3.0.zip from the 0.3.0 release, unzip it, and put its bin directory on your PATH. It runs on the java in JAVA_HOME, or on the PATH, which must be JDK 25 or later.

unzip mutastic-0.3.0.zip
export PATH="$PWD/mutastic-0.3.0/bin:$PATH"
mutastic --version

Then, in a Gradle or Maven project’s directory:

mutastic run

Next: the Quickstart runs mutastic on a small sample and closes the gap it finds.