The more I look at it the more I think intelliJ it...
# spring
p
The more I look at it the more I think intelliJ itself should support scanning for
@ConfigurationProperties
as part of its Spring support
y
could you please explain what doesn’t work for you? please note that recently bug in this area was fixed https://youtrack.jetbrains.com/issue/IDEA-188277
p
I use Maven with kapt to generate the metadata. However, it only generates the metadata from the top level properties. It ignores nested classes. IntelliJ (usually) correctly loads the metadata file but in my opinion it should just analyze the code automatically and not rely on having the metadata file generated by another tool.
y
the metadata is the only truth, we cannot and do not want to duplicate the work the annotation processor is doing.
please check with Spring Boot team directly if you think that AP is not working as expected in your case