Skip to content

feat: manage the swagger artifacts in the BOM - #3349

Merged
bnasslahsen merged 1 commit into
spring-boot-3from
backport/3325-bom-swagger-artifacts
Sep 6, 2026
Merged

feat: manage the swagger artifacts in the BOM#3349
bnasslahsen merged 1 commit into
spring-boot-3from
backport/3325-bom-swagger-artifacts

Conversation

@bnasslahsen

Copy link
Copy Markdown
Collaborator

Backport of #3346 to the Spring Boot 3 line.

Modules that only carry the swagger annotations had no way to pick up the version springdoc resolves elsewhere: importing the BOM copies its managed dependencies, not its properties.

swagger-annotations-jakarta, swagger-models-jakarta and swagger-core-jakarta are now managed by springdoc-openapi-bom. Its flattened form has to keep the properties for ${swagger-api.version} to be resolvable by the consumer, so flatten-maven-plugin switches from <properties>remove</properties> to <properties>expand</properties>.

Fixes #3325

Modules that only carry the swagger annotations had no way to pick up the
version springdoc resolves elsewhere: importing the BOM copies its managed
dependencies, not its properties. They are now managed by the BOM, whose
flattened form has to keep the properties for ${swagger-api.version} to be
resolvable by the consumer.

Fixes #3325

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@bnasslahsen
bnasslahsen merged commit 91bf7ee into spring-boot-3 Sep 6, 2026
1 check passed
@bnasslahsen
bnasslahsen deleted the backport/3325-bom-swagger-artifacts branch September 6, 2026 09:28
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

Successfully merging this pull request may close these issues.

1 participant