I think it would be nice with enforced sorting and...
# refreshversions
e
I think it would be nice with enforced sorting and sectioning in
versions.properties
to make it easier to navigate. Something like:
Copy code
## Plugins (alphabetically sorted on substring after `plugin.`)
plugin.com.adarshr.test-logger=3.1.0

plugin.com.github.johnrengelman.shadow=7.1.0

plugin.org.jlleitschuh.gradle.ktlint=10.2.0


## Custom notations (alphabetically sorted on substring after `version.`)
version.kotest=4.6.3

version.kotlin=1.6.0

version.ktor=1.5.3


## Generated identifiers (alphabetically sorted on substring after `version.`)
version.org.mock-server..mockserver-core=5.11.2

version.org.postgresql..postgresql=42.3.1
What do you think?
l
We don't want to enforce that sorting because folks might have good reasons to change the order. refreshVersions sorts keys alphabetically by default on each insertion though, why do you want it to prevent reordering?
👍 1
e
Oh, I never realized it was doing that. Over time, my
versions.properties
has gotten very un-sorted and it's just messy to find things in. But I guess I got myself to blame in that case. I get your point. Perhaps there could be a re-arrange/sort task that would need to be invoked manually?
l
You can sort them yourself, and then, if refreshVersions adds other entries, they should be at the right place.
e
👍