Manage plugin versions and related dependencies through custom alias rules

I’m not sure whether to consider this a bug or a feature request (namely, I do not know if the current behavior is there by purpose, if it is an unintended/unspecified behaviour, or if it does not behave as expected)

Describe the bug

Adding custom alias rules may intertwine badly with plugins version management. Consider, e.g.:

plugin.io.gitlab.arturbosch.detekt=1.9.1
version.io.gitlab.arturbosch.detekt..detekt-formatting=1.9.1

Since these two versions must remain aligned, it would be useful to group them into a single versions.properties entry, e.g. by

io.gitlab.arturbosch.detekt:*
                     ^^^^^^

This correctly produces a single version.detekt=1.9.1 entry. However, from this point on, the plugin can no longer get resolved.

To Reproduce

If necessary, I can produce a minimal project using the two plugins mentioned above. Let me know.

Expected behavior the plugin and its dependencies are pulled in with the version specified in the versions.properties file

[LouisCAD]

@DanySK This works:

Version key rule:

io.gitlab.arturbosch.detekt:detekt(-*)
                     ^^^^^^

version.properties file:

plugin.io.gitlab.arturbosch.detekt=version.detekt

version.detekt=1.9.0
## # available=1.9.1
## # available=1.10.0-RC1

[DanySK]

Yes this looks like a reasonable workaround! Thanks!