Version Catalogs and Multiple Plugins from Same Dependency

Help/Discuss
1

I’m using Gradle 7.2 and have the VERSION_CATALOGS feature enabled for experimentation. In editing the libs.versions.toml file I’ve included two entries in the [plugins] section with different ids and the same version.ref. It just so happens that these plugins have different marker files, but ultimately are sourced from the same dependency and so resolving the first does put both on the classpath. When it comes time to apply the plugins in a project, the 2nd one that is encountered generates the following error: “Plugin request for plugin already on the classpath must not include a version.”

gradle/libs.versions.toml

[versions]
commonPluginApi="1.0.0"

[plugins]
abc = { id = 'abc', version.ref="commonPluginApi" }
xyz = { id = 'xyz', version.ref="commonPluginApi" }

build.gradle

plugins {
   alias(libs.plugins.abc)
   alias(libs.plugins.xyz)
}

Using the plugin management declaration and corresponding references in a project build.gradle doesn’t seem to trigger this same issue.

settings.gradle

pluginManagement { 
   plugins { 
      id = 'abc'  version = '1.0'
      id = 'xyz' version = '1.0'
   }
}

build.gradle

plugins {
   id 'abc'
   id 'xyz'
}

Does this sound like an issue in the version catalog feature or is it a limitation where plugins should not be packaged together in general?