[pjmlp]

Android studio and everything that depends on the Gradle integration deep within it.

For example, I do actually like XML, but when I looked at it I came out with the idea that I could not use the visual tooling any longer, rather some Scala DSL.

[airless_bar]

Ah alright. yes, I think it makes more sense to define the GUI with code. Typed resources help with it.

sbt-android-gradle has full support for Gradle projects, but to be honest: Gradle is utter shit. Just use the SBT plugin. it works so much better. The latest version even manages SDK and NDK for you.

[vorg]

I don't like having to use a different language (i.e. Apache Groovy) to write build scripts when using Gradle with Scala. With SBT, I write Scala to build Scala, see [1]. I can see why someone would use Groovy to build a Groovy project, but why should I use 20 lines of Groovy to build Scala?

I notice Kobalt [2] for Kotlin is still being actively developed, and Leiningen for Clojure, both using the syntax of the language they're compiling for their build DSL. If Gradle won't become language agnostic for specifying its build scripts instead of shoving something else down people's throats, people will elsewhere, or stick with Maven.

[1] http://alvinalexander.com/scala/sbt-syntax-examples

[2] https://github.com/cbeust/kobalt

[pjmlp]

I agree with your opinion, if it wasn't for Android I very much doubt anyone would care about Gradle.

Have to try it out again.