VSCode PROP_UNKNOWN_PROPERTY when using spring-boot-configuration-processor in a Gradle project
See original GitHub issueDescribe the bug In VSCode when using spring-boot-configuration-processor in a Gradle project, any custom properties report PROP_UNKNOWN_PROPERTY.
This issue does NOT occur when using a Maven project.
To Reproduce
- Install Spring Boot Extension Pack
- Initialize a new Spring Boot Gradle project with
spring-boot-configuration-processor
- Create a new
@ConfigurationProperties
class - Attempt to set newly created properties in
application.properties
Sample https://github.com/mdgilene/spring-unknown-config-bug
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Spring Boot support in Visual Studio Code
Spring Boot extensions for Java developer using Visual Studio Code editor. ... to start generating a Maven or Gradle project and then follow...
Read more >Why can't VSCode detect this project structure generated by ...
I'm new to Gradle and I've generated a Gradle application project using the gradle init. It's working fine when I run gradle run,...
Read more >Spring Boot Hellow world gradle application generation using ...
generate the spring boot gradle project using vscode editor.How to generate spring boot project using vscode editor.
Read more >How do I configure VS Code and Gradle to use generated ...
I'm trying to use Protobuf with Google's official Gradle plugin, with Gradle, in VS Code, in a small Java application to test out...
Read more >Spring Functionality, Debugging Improved in Java on VS ...
The regular monthly update to Java on Visual Studio Code sees ... the Java Project Explorer view in a Maven or Gradle project...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@RamenTurismo I would recommend to comment on the above mentioned issue of the buildship project…
This is expected because Gradle tooling (BuildShip) doesn’t support annotation processor configuration in Eclipse. The maven tooling (m2e) does.
This is a very long standing issue. See: https://github.com/eclipse/buildship/issues/329
You can try to comment there to try and add your vote/voice and motivate Gradle folks to fix this.