Skip to content

Automatically filter additional configuration metadata from Spring Boot-built archives - #51386

Open
Wanbinyu wants to merge 1 commit into
spring-projects:mainfrom
Wanbinyu:gh-27430-filter-additional-configuration-metadata
Open

Automatically filter additional configuration metadata from Spring Boot-built archives#51386
Wanbinyu wants to merge 1 commit into
spring-projects:mainfrom
Wanbinyu:gh-27430-filter-additional-configuration-metadata

Conversation

@Wanbinyu

Copy link
Copy Markdown

This updates Spring Boot's Maven and Gradle packaging support to exclude META-INF/additional-spring-configuration-metadata.json from built archives. The additional metadata has already been merged into spring-configuration-metadata.json by the annotation processor.

The loader tools filter the metadata relative to the layout's classes location, covering both jars and wars. Gradle boot archives apply the equivalent default exclusion. The documentation also shows how to configure the exclusion when building a library without either Spring Boot plugin.

Closes #27430

Signed-off-by: Wan bin yu <3431359639@qq.com>
@Wanbinyu
Wanbinyu force-pushed the gh-27430-filter-additional-configuration-metadata branch from 3d60308 to 3744c18 Compare August 17, 2026 05:30
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status: waiting-for-triage An issue we've not yet triaged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Automatically filter additional-spring-configuration-metadata.json from Spring Boot-built archives

2 participants