This message was deleted.

had a very similar issue. iirc, tried with

--refresh-dependencies

first and think I ended up removing ~/.gradle/caches.

I bumped to 1.7.21 (which was released today I think)

The embedded Kotlin with Gradle is 1.7.10, best to stick with that for Gradle components (such as the referenced plugin-api).

ah embedded Kotlin!

yep, the root of both goodness… and challenges…

Removing ~/.gradle/caches, see you in a bit !

ok. Presuming this is a Gradle plugin. Ensure this is correct:

plugins {
    `kotlin-dsl`
    // DO NOT use kotlin("jvm") here as this is a Gradle plugin that will use the embedded Kotlin, pulled in by `kotlin-dsl'
    // also: it's redundant to use `java-gradle-plugin` (already pulled in by `kotlin-dsl`
}

I'm using

plugins {
  `embedded-kotlin`
  id("java-gradle-plugin")
}

ouch. that’s likely part of the problem. partial setup,

kotlin-dsl

does what you need.

clutters the global namespace

it won’t work w/o it - that’s what pulls in the Gradle API. You want

kotlin-dsl

to write Gradle stuff.

I've done this before

not following why

kotlin-dsl

isn’t being used to pull in the standard set of things?

Turns out it's the "java-gradle-plugin" that seem to mess with resolution 🤔

perhaps flip the order? In

kotlin-dsl

they’re done in a different order:

apply<JavaGradlePluginPlugin>()
        apply<KotlinDslBasePlugin>()
        apply<PrecompiledScriptPlugins>()

…the middle one is embedded kotlin.

Ah, good call, trying it

This is working on 7.6-rc-2:

plugins {
    `embedded-kotlin`
    `java-gradle-plugin`
}

repositories {
    mavenCentral()
}

The

kotlin-gradle-plugin:1.7.21

is the one that fails to resolve

yea, guessing that is pulled in by the embedded kotlin. How was the 1.7.21 version specified? only seeing 1.7.10 resolved.

Mmmm this is working as well... I'll dig

plugins {
  id("java-gradle-plugin")
  `embedded-kotlin`
}

repositories {
  mavenCentral()
}

dependencies {
  implementation("org.jetbrains.kotlin:kotlin-gradle-plugin:1.7.21")
}

even with the above it still pulls in kotlin-gradle-plugin (and other stuff) at 1.7.10. Visible via

./gradlew --refresh-dependencies --info | grep https

. Something else must be forcing 1.7.21.

Alright, it all boils down to this:

plugins {
  id("java-gradle-plugin")
  `embedded-kotlin`
}

repositories {
  mavenCentral()
}

dependencies {
  implementation("org.jetbrains.kotlin:kotlin-gradle-plugin:1.7.21")
  implementation("org.jetbrains.kotlin:kotlin-allopen:1.7.10")
}

that appears to work … wait … it fails when doing

./gradlew test

.

It fails to resolve the configuration

yea. wondering if forcing version alignment will fix this, trying that…

That explains why it's caused by the "java-gradle-plugin"

yea. have something in a plugin convention plugin to align Kotlin component versions, endless problems there…

Still a bit surprising but at least that solves my issue. Thanks for the help!

np. cheers.