Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VSCode PROP_UNKNOWN_PROPERTY when using spring-boot-configuration-processor in a Gradle project #585

Closed
mdgilene opened this issue Jan 10, 2021 · 5 comments
Assignees

Comments

@mdgilene
Copy link

mdgilene commented Jan 10, 2021

Describe 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

  1. Install Spring Boot Extension Pack
  2. Initialize a new Spring Boot Gradle project with spring-boot-configuration-processor
  3. Create a new @ConfigurationProperties class
  4. Attempt to set newly created properties in application.properties

Sample
https://github.com/mdgilene/spring-unknown-config-bug

@martinlippert martinlippert added this to the 4.9.1.RELEASE milestone Jan 14, 2021
@kdvolder
Copy link
Member

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: eclipse-buildship/buildship#329

You can try to comment there to try and add your vote/voice and motivate Gradle folks to fix this.

@martinlippert martinlippert removed this from the 4.9.1.RELEASE milestone Jan 20, 2021
@emyfreya
Copy link

emyfreya commented Jan 7, 2022

I am from the future and here to motivate gradle folks to fix this!
Getting the configuration right the first time without looking into the code is really a gain of time, especially on big projects.

@martinlippert
Copy link
Member

@RamenTurismo I would recommend to comment on the above mentioned issue of the buildship project...

@gratisCobalt
Copy link

I got the same issue with a maven project

@martinlippert
Copy link
Member

@gratisCobalt Can you share more details about when and how you are running into this issue and provide a few steps to reproduce this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants