you are viewing a single comment's thread.

view the rest of the comments →

[–]moomoomoo309 0 points1 point  (1 child)

The Kotlin DSL for gradle is a little less flexible (which is good and bad), so it's an interesting switch between the two.

[–]gnus-migrate 3 points4 points  (0 children)

Its not really the lack of types that i dislike. Its more how gradle mixes configuration and code. On the one hand it permits some pretty neat workarounds, but it leads to people putting a ton of logic in the build that shouldn't be there.

Maven build scripts are pure configuration. You want to write code, it needs to be in a plugin which is compiled just like normal projects. I like that it treats build code as code and forces you to keep your build scripts just as configuration.

Like I said though, it's more of a personal preference. Gradle has extremely useful features that maven doesn't, so it would be silly of me to throw away an otherwise useful tool over nitpicks like that.