This message was deleted.

@Eug Hi 👋 If I get it right in your

$root/build.gradle

file you have

plugins {
alias(libs.plugins.jetbrains.kotlin.serialization) apply false
    alias(libs.plugins.jetbrains.kotlin.serialization.new) apply false // some alias
}

If you want then use specific plugin over another let say in

app

module you can define it as follow in

app/build.gradle

plugins {
  alias(libs.plugins.jetbrains.kotlin.serialization.new)
}

Aha, thanks!

It is possible to apply plugin with alias. You are not restricted with

id 'whatever'

syntax

gradle complaints that version in the root file is unknown and it can not compare it

The main question actually is: why do you add plugins to your root script with

apply false

? What are you trying to solve by doing this? Most of the time, this was used to manage versions in a central place (the root script), but then

pluginManagement { plugins }

was added to the settings, and then version catalogs (that you're using here). There are probably a few cases where you'd need to "hoist" plugins to that root project's classloader but they should be very rare. TL;DR: with

pluginManagement { plugins }

or version catalogs, you shouldn't need

apply false

any longer anyway, so just declare plugins in the modules where you need them.

Interesting! I think we added version catalogue at some point and didn’t understand that this section is redundant now