Hi Everyone, I posted this in the wrong channel (b...

# gradle

[Anonymike]

Hi Everyone, I posted this in the wrong channel (before realizing there was a gradle channel) and @e5l tried to help out, but this is really disrupting my work at the moment.

Our team upgraded all our core libraries and projects to kotlin 2.1.21 and everyone can build the projects fine except me. I haven't been able to identify the difference. I am able to build projects if I downgrade to 2.1.20. We use gradle wrapper and are on the same Gradle versions as well. I know this particular feature relates to a surprise deprecation by gradle. We're on Gradle 8.14.1 now, but have tried all the way back to 8.12.1.

This is the error message that happens about 500ms after running the build command:
Unable to find method ''org.gradle.internal.buildoption.BuildOption$Value org.gradle.api.internal.StartParameterInternal.getIsolatedProjects()''

More info in thread...

Any help is greatly appreciated! Right now to work on anything I have to downgrade every build involved to 2.1.20, do my work, avoid committing the changed version and rely on the rest of my team for final testing because I cannot run any 2.1.21 project.

[Anonymike]

gradle-stacktrace.txt

gradle-stacktrace.txt

[Anonymike]

Small addition: This occurs in all of my projects...server, simple cli utilities, libraries, etc. Anywhere I use 2.1.21 I get the same error. The moment I downgrade to 2.1.20 it builds fine.

Gradle --stacktrace output attached. Line 9 refers to applying the kotlin gradle plugin.

I've also tested all combinations of the following two properties and I get the same error. I tried them both in the projectfolder/gradle.properties and in my home folder ~/.gradle/gradle.properties on my linux system.

# 20250529: Gradle Isolated Projects Feature
org.gradle.unsafe.isolated-projects=false
# 20250529: Kotlin 2.1.20: Isolated Projects Support
kotlin.kmp.isolated-projects.support=enable

To be clear, I tried the following combinations:
• true/enable both
• false/disable both
• false gradle, enable kmp
• true gradle, false kmp

[wasyl]

If you can publish a build scan it might show you where your build differs from the ones that work.
Other than that, are you on the same java version? Anything in your ~/.gradle/init.gradle? Does a ./gradlew <build task> --gradle-user-home=/fresh/temporary/gradle/home-dir work?

[Anonymike]

Thanks for the response @wasyl!
• Java Version is the same. We use sdk man and strictly keep the same jvm's installed.
• We do have init.gradle.kts in our home folders for common settings and I've set properties in that as well as locally in the project.

[Anonymike]

I should also mention I've done a fresh build and completely deleted my ~/.gradle folder as well.

[tapchicoma]

are you using Gradle to download plugin jars or some externally populated cache?

[tapchicoma]

Most probably you are hitting this problem because Kotlin Gradle Plugin jar was not downloaded by Gradle itself

[Anonymike]

We use reposilite to proxy and cache our dependencies (its a fantastic project btw). I'll go in and try to delete all the gradle plugin caches and see what happens.

[Anonymike]

@tapchicoma I added the default plugin repository before our caching one and did a build clean, then rebuilt and it worked. I'm going to open an issue with Reposilite after doing some more research to determine what needs to be done for it to support serving the correct variant to gradle.

In a related note, you have descended from the heavens and saved my troubled soul from the Gradle hellscape I was doomed to. How can I thank you or at least buy you a coffee for your kindness?

[Anonymike]

I saw at least three of these fly by after my successful build. They smile upon us.

[Anonymike]

Hey @wasyl, that coffee/tea offer and gratitude goes for you too. I appreciate you trying to help as well.