specially when considering all tooling that comes for free with

*.kts

Yep

build.kts

?

I have always wondering about the long and strange

.gradle

file extension

or

gradle.kts

gradle.kts

would rock IMO

and be consistent with

gradle.properties

Using

gradle

sometimes for file extension, sometime for filename is confusing

gradle.kts

is consistent and logical IMO

And elegant 😉

And if you plan was to detect

*.gradle.kts

, just autodetect

*gradle.kts

That would match with this beautiful

gradle.kts

filename I could use with my

gradle.properties

to acheive beautiful project layout 🙂

@bamboo so how do I create a child project in root script?

@sdeleuze

*gradle.kts

looks doable, will you please add an issue to github?

@bamboo Sure with pleasure

@sdeleuze

build.gradle

is only the default and actually something we regret. Really, every project should have specific name like foo.gradle and bar.gradle. You can of course configure it that way. Using the same file extension is a bad idea in my opinion. You can’t easily tell the language without invoking an expensive parser.

yeah I agree about using the same extension not being a good idea

But I see using a convention like

gradle.kts

as a nice default convention at least for my projects

When I have submodule the subdirectory already indicates the module name

but when you type

.gradle

in your IDE it’s nice when every one of them is different at a glance

that’s my personal preference at least, instead of having to read the full paths, especially when they are long and pruned

In any case,

*gradle.kts

detection could allow both practices

Just to be clear though: The default would still be build.gradle.kts

We don’t scan the project directory for build files, the user specified it up-front in

settings.gradle

. The regex pattern is only used by the IDE to decide which files to provide completion for

Hum, sad,

build.gradle.kts

looks very ugly from my POV

I mean you could argue for changing the default

Ok, I will

I updated the issue with a note that explain I changed the scope after your feedback

And I am going to create a Twitter poll for that