This message was deleted.
# community-support
s
This message was deleted.
c
Expected. Dash, underscore, and dot are separators, resulting in the same accessor name. You could have the generator add some suffix if the artifact ends with a separator - or fix the unusual naming convention of an underscore suffix (perhaps a proper qualifier is needed).
Aliases must consist of a series of identifiers separated by a dash (
-
, recommended), an underscore (
_
) or a dot (
.
). Identifiers themselves must consist of ascii characters, preferably lowercase, eventually followed by numbers.
g
uhm, thanks
v
I'm actually surprised it works with sepeartor at the end. I'd almost expected that to be a naming violation.
d
Isn’t there a difference in what is allowed in aliases in Kotlin DSL versus Groovy DSL? It’s been a while since I looked at it, but I recall the Kotlin DSL being a bit more forgiving in the names.
v
I'd wonder if there were, that would be majorly confusing
c
indeed. the rules for aliases are clearly documented, with no distinction between Kotlin & Groovy.
d
Ahh, looking at my project, I was thinking of an alias oddity for plugins that we ran into before moving to a version catalog when using something like
ext.libraries
There were nuances in plug in naming before then that would throw an error of
argument list must be exactly 1 literal String or String with property replacement