Gradle support

Qoddi’s Gradle buildpack uses Gradle to build your application and OpenJDK to run it.

Usage

Commit the Gradle Wrapper: gradlew, gradlew.bat, gradle/wrapper/gradle-wrapper.jar, and gradle/wrapper/gradle-wrapper.properties. Keep gradlew executable. Use build.gradle or build.gradle.kts for the build definition.

As of November 2, 2026, the classic Heroku buildpack supports Gradle 8.x and 9.x and recommends 9.x. Select a tested distribution through the wrapper.

The classic default task is stage, with framework-specific alternatives such as build for Spring Boot and Quarkus or shadowJar for Micronaut. GRADLE_TASK overrides that choice. Ensure the task packages all runtime dependencies and test it locally.

Specify a Java version

Select the JDK in system.properties; see Java runtime selection. Match your Gradle wrapper and plugins to that JDK using Gradle’s compatibility matrix. For example, running Gradle on Java 25 requires Gradle 9.1.0 or later.

Default web process type

Provide a Procfile that launches the artifact your build produces. For an executable Spring Boot JAR named my-app.jar:

web: java -Dserver.port=$PORT -jar build/libs/my-app.jar

Use the actual filename, or the start script generated by an application distribution. Avoid an ambiguous *.jar path when both executable and plain JARs are produced.