I had a short chat with @bamboo about this idea at Kotlin Conf.

Currently the init task which invokes the Maven2Gradle converter only supports generating groovy based DSL.

Expected Behavior

Ability to convert a maven project to the Gradle Kotlin DSL OR Gradle Groovy DSL.

Current Behavior

Currently, only Groovy is supported.

Context

This would help increase adoption of the Gradle Kotlin DSL for users that are migrating their builds from maven.

Questions

• Does this converter make sense to live in the Gradle repository or the Kotlin DSL repository?
• If the converter should live in the Gradle repository, can the logic that already exists in the Maven2Gradle class be shared with the Kotlin converter? Does it make sense to share logic between the two converters or try and write a new one for Kotlin?
• The MavenProjectsCreatorSpec doesn't seem to actually compile the generated build file. Is there a different place where that does happen?

Does anyone know how often this converter gets used? I know that I ran it when I was first attempting my conversion of my companies build from Maven to Gradle and found it an incredibly useful starting point. Is it worth spending the time to implement the converter for Kotlin?