This message was deleted.

I also did not see this in the release notes. Maybe @Xavier Ducrohet would know?

I just found out that I can use

lintClassPath

in module

build.gradle

but not anymore in root

build.gradle

in

subprojects {
dependencies {}
}

It's best not to configure all modules inside

subprojects

and instead use conventions plugins. Here is an example: https://docs.gradle.org/current/samples/sample_sharing_convention_plugins_with_build_logic.html

Thanks. I will look at that. Anyway global configuration was really useful. Our project has about 150 modules and during java migration we could change java version only in one file instead of modifying 150 files…

subprojects {
android {
            compileOptions {
                sourceCompatibility JavaVersion.VERSION_11
                targetCompatibility JavaVersion.VERSION_11
            }

            kotlinOptions {
                jvmTarget = '11'
            }
        }

        tasks.withType(org.jetbrains.kotlin.gradle.tasks.KotlinCompile).all {
            kotlinOptions {
                jvmTarget = '11'
            }
        }
}

Same for shared dependencies (

VersionCatalog

is good alternative) Test configuration, etc…

Exactly, yes you can do that with a convention plugin