Convention over Configuration

[brunoborges]

Hey all,

I just watched the recent presentation about Mill, and the performance benefits are undeniable.
However, I feel that the core benefit of having a build tool (and in particular Maven) in the first place is still missing: conventions.
Right now, the build file is a script, a code, that must be programmed to configure the build flow.

This has been, historically, one of the main reasons for Gradle's slow adoption and conversion rate over Maven.

Looking at a Maven build file when knowing the Maven conventions, is straightforward.
Looking at a Gradle build file, even when knowing the usual Gradle constructs, can raise questions, because developers can write however they want, and extensively customize it.

So, I'd like to ask if folks working on Mill have thought of a second model that follows Maven's philosophy.