Can I silence the "kotlin-compiler-embeddable Arti...

# gradle

[Josh Friend]

Can I silence the "kotlin-compiler-embeddable Artifact Present in Build Classpath" somehow? I understand the problem it is raising and will address it, but I want to get rid of the thousands of logspam messages it throws during every build while I'm fixing it.

[Adam Semenenko]

hi, please try suppressing the warning by adding this line to in your project's gradle.properties file.

Of course this should only be done temporarily. kotlin-compiler-embeddable in buildscript classpaths will cause hard to diagnose build issues. I recommend putting a reminder TODO.

# TODO remove after root cause fixed
kotlin.suppressGradlePluginWarnings=KotlinCompilerEmbeddableIsPresentInClasspath

[mbonnin]

I never really understood this warning. How is kotlin-compiler-embeddable special? Isn't it the same for every dependency in build scripts?

[Adam Semenenko]

The KCE dependency is a bit different not because a specific version is needed, but because KGP will no longer align the version

KGP removed KCE as a dependency in v2.1.0 KT-61706.

Prior to v2.1.0, if multiple plugins depended on KCE then Gradle can only resolve a single version, and typically this was the KGP version.

But with v2.1.0, since KGP doesn't have a dependency on KCE it won't be used for alignment. Some other plugin could depend on a really old KCE version and cause very strange issues (example: KT-73761).

[mbonnin]

Isn't the issue that kotlinter and kgp depended on conflicting versions of KCE?

[mbonnin]

Since there can be only one, Gradle resolved the highest one but that made kotlinter fail?

[mbonnin]

Other issue is Gradle not always correctly resolving the highest version because buildSrc classpath clobbers everything

[mbonnin]

But this is the same for every dependency of KGP or any other plugin I think?

[mbonnin]

In all cases, dropping the dependency in 2.1 is cool 👍👍

[Josh Friend]

we have an old sqldelight plugin version that is causing this dependency, and i dont want to have to deal with that just to update kotlin (which is more urgent). ill try the property, thanks!