The additional-spring-configuration-metadata.json file is unnecessarily landing in generated modules JARs: refer to spring-boot-autoconfigure.jar as an example.
I assume this is unnecessary as the contents are already merged on spring-configuration-metadata.json produced by spring-boot-configuration-processor, and STS/plugins will not read it when the source is a JAR file.
The proposal is to exclude it from build resources so that build plugins can ignore it when producing the JAR artifact.
ps: Im not creating an issue since this is a very small contribution
Comment From: wilkinsona
Thanks for the suggestion. If this is something that we want to do, we'd need to do it for both Maven and Gradle. We may also want to consider doing it in a way that'll work for people who aren't using spring-boot-starter-parent. For example, it could be implemented as part of repackaging in spring-boot-maven-plugin.
I think it might be best if you opened an issue to track the possible enhancement. We can then decide if it's something that we want to do and, if it is, discuss the best way to implement it. Thanks anyway for the pull request.