recently I saw more and more Maven/Gradle Kotlin p...

# announcements

[alex]

recently I saw more and more Maven/Gradle Kotlin projects that have a non-standard Gradle/Maven structure like <PROJECT_ROOT>/src/my/package instead of the classically conventional <PROJECT_ROOT>/src/main/kotlin/my/package. Basically the main/kotlin infix disappeared. Also the resources are on the same level as the src folder.

Is this the new project structure that Kotlin wants to adopt and become mainstream? Or are those just some odd cases?

[gildor]

As I know, It’s just a structure of project that guys from JetBrains appreciate more than default src/main/kotlin from Maven and Gradle.
Ilya Ruzhenkov from JB mentioned it in some chat here.
But I don’t think that they push it for everyone or even try to use as default structure for everyone.

[jimn]

for code generators, change is really really bad

[jimn]

writing maven plugins with senible defaults resists hierarchy flexibility

[gildor]

There are a lot of possible pitfalls if you want to do that as structure by default (for example big problem for Android), but for you own project I think it’s fine

[jimn]

when i write a protobuff compiler, i prefer src/main/proto

[jimn]

there is a lot of gymnastics involved in generating classes and packaging to war

[jimn]

the less moving parts the quicker im done

[jimn]

iirc android development clung to ant a very very long time.

[jimn]

it sounds like it embodies the very reason why not to cling to scripted build [platforms