Are there are any conventions for aliases in version catalogs? This is my informal convention thus far: 1. Use two levels: one for the group, one for the artifact. E.g.:

guava-guava

,

guava-testlib

, where

guava

(first level) is an alias for the

com.google.guava

group,

guava

(second level) is an alias for the

guava

artifact, and

testlib

is an alias for the

guava-testlib

artifact. 2. One word is preferred for each level, but when multiple words are better, use camel case. The canonical example:

junitJupiter-api

3. For plugins, the first level is

plugin

, and the second level is a descriptive name. E.g.:

plugin-spotless

,

plugin-errorprone

(I have mixed feelings on aliases--it feels less readable, and different people may use different aliases for the same dep--but I wanted to make the aliases feel more like a proper dependency and less haphazard.)