The right link for the kapt issue is in fact <https://youtrack.jetbrains.com/issue/KT-15040#comment=...

# spring

[sdeleuze]

The right link for the kapt issue is in fact https://youtrack.jetbrains.com/issue/KT-15040#comment=27-2840615

[poohbar]

weird thing.. even if i somehow manage to generate the right metadata file (gradle or maven), intellij still puts warning on every property.. it says it is looking for:

META-INF/additional-spring-configuration-metadata.json

It should be looking for:

META-INF/spring-configuration-metadata.json

which is there 😄

[sdeleuze]

Strange with my tests on MiXiT or the attached project in that issue that works after runnung commd line

[sdeleuze]

What IDEA version and Kotlin plugin version ?

[poohbar]

Idea is on 2018.1.2

[poohbar]

Kotlin is on 1.2.40

[poohbar]

but it's quirky.. i swear it worked yesterday but it doesnt now

[sdeleuze]

Hum

[poohbar]

and when I use Build / Rebuild Project, the metadata dissapears.. but I guess thats expected since the Idea build does not process annotations?

[sdeleuze]

Yes

[poohbar]

ok, then the only weird thing is idea not seeing the metadata

[sdeleuze]

Do you have an additional metadata file in your project as described in https://docs.spring.io/spring-boot/docs/current/reference/htmlsingle/#configuration-metadata-additional-metadata or not ?

[sdeleuze]

It could just come from support for that

[poohbar]

no, i dont use that feature.. but the idea quickfix asks me if i want to create it

[sdeleuze]

Ok, so that's expected

[poohbar]

ok

[sdeleuze]

The real issue remains KT-15040

[sdeleuze]

I said to Kotlin team this is a critical one

[sdeleuze]

Since super confusing for a lot of people

[poohbar]

that definitely is an issue but I guess I have also a separate issue

[sdeleuze]

Feel free to raise one and share here if you acheive to identify it clearly

[poohbar]

will do

[poohbar]

Very confusing indeed. It seems that the:
spring-boot-configuration-processor
has to be on the classpath otherwise intellij refuses to resolve the properties (there is probably some sort of check for this in the IDE itself).. however the properties get messed up by java compiler if the processor is there. Solution is to set the spring boot processor's scope to runtime.

Then the properties wont get messed up and intellij is happy too.

[poohbar]

Really starting to feel like Maven users are getting less and less love from both Spring and JetBrains 😞