hey! after having created a new spring initializr ...

# getting-started

[Erik Aaron Hansen]

hey! after having created a new spring initializr project through intellij I get this error in the project:

Classes annotated with '@Configuration' could be implicitly subclassed and must not be final

I've looked at the docs here: https://kotlinlang.org/docs/all-open-plugin.html, but the dependency id("org.jetbrains.kotlin.plugin.allopen") version "1.3.72" is already inside build.gradle.kts. are there other steps necessary after creating a new project? I'm using 11.0.11.hs-adpt as sdk.

[Joffrey]

"All open" is generic, and needs to be configured so you tell it which annotation should force the class to be marked open.

However, since Spring is so common, there is another plugin that is a superset of all-open, but with preconfigured annotations for Spring specifically:

plugins {
  id "org.jetbrains.kotlin.plugin.spring" version "1.5.31"
}

It's described a bit lower on the same doc page: https://kotlinlang.org/docs/all-open-plugin.html#spring-support

[Joffrey]

@Configuration-annotated components should be marked open out of the box with this Spring plugin

[Erik Aaron Hansen]

thanks for explaining. if I replace the allopen dependency with the one you mention, I get an error: "Plugin with id 'org.jetbrains.kotlin.plugin.spring' was already requested at line 3". this is my plugins now:

[Erik Aaron Hansen]

Untitled.txt

Untitled.txt

[hfhbd]

Just use this:

plugins {
    id("org.springframework.boot") version "2.5.6"
    id("io.spring.dependency-management") version "1.0.11.RELEASE"
    kotlin("jvm") version "1.5.31"
    kotlin("plugin.spring") version "1.5.31"
}

[Joffrey]

@Erik Aaron Hansen Actually the line kotlin("plugin.spring") is completely equivalent to id("org.jetbrains.kotlin.plugin.spring") , so you're declaring it twice.

(Side note, I just mentioned the latest Kotlin version in my snippet, but you should use the same one for all Kotlin plugins - but 1.3.72 is pretty old, and Spring 1.0.11.RELEASE actually uses 1.5.31 I believe)

[Erik Aaron Hansen]

I see. okay, so I tried Philip's minimal list of plugins, but I still get the red squiggly line with the same error I mentioned above

[Joffrey]

Do you get this error when running gradle via CLI?

[Erik Aaron Hansen]

is there something wrong with the configuration of my code inspection tool?

[Erik Aaron Hansen]

no 🙂

[Joffrey]

Then maybe your IDE is not properly synchronized with Gradle I guess, which one are you using?

[Erik Aaron Hansen]

which gradle? I don't have it pre-installed

[Erik Aaron Hansen]

according to gradle-wrapper.properties, 7.2

[Joffrey]

What I mean is that your IDE uses Gradle (through the wrapper in your case) to get information about dependencies and compiler plugins etc. In intelliJ IDEA for instance you can use the "reload all projects" button from the Gradle panel.

[Erik Aaron Hansen]

oh, yeah I use the latest version of IntelliJ IDEA (2021.2.3)

[Joffrey]

If that doesn't work you can also use the "invalidate caches" action

[Erik Aaron Hansen]

I should mention I'm doing this on wsl but I'm sure this haven't been a problem earlier

[Erik Aaron Hansen]

I tried what you suggested, I even deleted the ~/.gradle folder, but I still get the same

[Joffrey]

There is also a .gradle directory in your project folder that you can try to remove. But I still find this strange. I'm sorry I'm running out of ideas here

[Erik Aaron Hansen]

thanks for trying 🙂

[Alexey Belkov [JB]]

There is a regression in IDEA 2021.3 EAP, maybe that's the problem: https://youtrack.jetbrains.com/issue/KTIJ-19864

[Erik Aaron Hansen]

I knew it had to be! thanks for posting 🙂

[Joffrey]

@Erik Aaron Hansen our search was doomed from the start 😄

[Erik Aaron Hansen]

yes Joffrey 😭