Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
spring-boot-configuration-processor doesn't work correctly for incremental builds #2313
This is a problem when the processor is used from Eclipse. It manifests when the project has more than one type annoted with @ConfigurationProperties.
The processor rewrites the metadata file with a summary of information from all the types it processed. This produces the correct result on FULL builds but produces incomplete information on incremental builds (as the processor is only presented with some of the types based on what has changed in the workspace since the last build).
The result is that on incremental builds information from non-changed types is deleted from the metadata file.
The project contains Eclipse metadata so it should enable Eclipse JDT APT when imported into STS as a 'Existing Project'.
This is how to reproduce the issue.
Note that in order to test changed snapshot of the processor you have to build a jar (i.e. run 'mvn install' on the processor project. This is because JDT APT can not consume a processor from a project directly, so unless you build the jar, you won't be running your changed version but whatever is in your local mvn repo).
Let me know if you need any help with this (I know JDT APT is finicky as hell).