Does this generate Groovy or Kotlin DSL?

It generates the classic Groovy build.gradle syntax, which is the most widely supported and the default for new Gradle projects unless you opt into build.gradle.kts. The dependency and plugin concepts map one-to-one to the Kotlin DSL.

What does the Java toolchain block do?

The toolchain block tells Gradle which JDK version to compile and run against, and Gradle will download a matching JDK if one is not installed. This makes builds reproducible regardless of the developer's local JAVA_HOME.

Why is mavenCentral() in the repositories block?

mavenCentral() tells Gradle where to fetch declared dependencies. Without at least one repository, Gradle cannot resolve anything beyond the standard library, so every real project needs it or an equivalent.

Is the output ready to run immediately?

It is a valid starting point but a stub — you still need a settings.gradle with rootProject.name and your actual source files. Treat it as the build configuration scaffold, not a complete project.

Gradle build.gradle Stub Builder

Q: What is the difference between implementation and testImplementation?

implementation puts a dependency on the main compile and runtime classpath, while testImplementation only exposes it to test source sets. Using implementation instead of the old compile keeps your API surface from leaking transitive dependencies.

Email me this result

Get this tool's output sent to your inbox, plus one useful tool a week. No spam, unsubscribe any time.

Generate a working build.gradle in seconds

A build.gradle file is the heart of any Gradle project: it declares which plugins apply, where dependencies come from, what libraries the code needs, and how tasks like test behave. Writing one by hand means remembering the exact plugin IDs, the difference between implementation and testImplementation, and the toolchain syntax. This builder assembles a correct, idiomatic file from a few choices.

How it works

The tool follows the standard Gradle JVM build layout. It always emits a plugins { } block (java plus application for runnable apps, or just java/java-library for libraries; the Kotlin JVM plugin is added for Kotlin projects). It sets group and version, configures a java { toolchain { languageVersion = JavaLanguageVersion.of(N) } } block so the build pins its JDK, and adds repositories { mavenCentral() }. Dependencies you type are split into implementation and testImplementation lines inside dependencies { }. Finally it adds tasks.named('test') { useJUnitPlatform() } so JUnit 5 tests run, and for applications a mainClass is wired into the application { } block.

Tips and notes

Use implementation for anything your own code imports, and reserve api (library projects) only for dependencies you intentionally re-expose.
Dependency coordinates follow group:artifact:version, e.g. com.google.guava:guava:33.0.0-jre.
For Kotlin, the generated file applies the org.jetbrains.kotlin.jvm plugin and adds the standard library automatically.
Pair this with a settings.gradle containing rootProject.name = 'your-project'; Gradle needs both to build.