Migrating from Gradle

This guide covers migrating from Gradle's settings.gradle or settings.gradle.kts to Antlers.

Quick Start

antlers init --from settings.gradle.kts

What Gets Migrated

Maven Repositories

Gradle maven { } blocks are imported:

Gradle (Kotlin DSL):

dependencyResolutionManagement {
    repositories {
        mavenCentral()
        maven {
            url = uri("https://maven.example.com/releases")
        }
    }
}

Antlers:

[[repositories]]
id = "central"
name = "Maven Central"
url = "https://repo1.maven.org/maven2/"
ecosystem = "maven"

[[repositories]]
id = "maven-1"
url = "https://maven.example.com/releases"
ecosystem = "maven"

Well-Known Repositories

Gradle shortcuts are recognized:

Authenticated Repositories

Gradle:

maven {
    url = uri("https://maven.pkg.github.com/org/repo")
    credentials {
        username = System.getenv("GITHUB_USER")
        password = System.getenv("GITHUB_TOKEN")
    }
}

Antlers:

[[repositories]]
id = "maven-1"
url = "https://maven.pkg.github.com/org/repo"

[repositories.credentials]
type = "basic"
username = { env = "GITHUB_USER" }
password = { env = "GITHUB_TOKEN" }

[env]
allow = ["GITHUB_USER", "GITHUB_TOKEN"]

Groovy DSL

Both Kotlin and Groovy DSL are supported:

Gradle (Groovy):

dependencyResolutionManagement {
    repositories {
        mavenCentral()
        maven {
            url 'https://maven.example.com/releases'
        }
    }
}

Limitations

The parser is line-based and does not evaluate Gradle logic. Review the output, especially when repositories are built dynamically or conditionally. Credentials are attached to the most recent repository block, and pluginManagement and dependencyResolutionManagement repositories are both scanned. Dependencies and version catalogs are not migrated.

Comparison