At concept level, there is nothing to add to #3212:
If springdoc declares supported swagger version in BOM, springdoc clients MAY import the BOM and be sure no conflict between springdoc and swagger
The only fact which happened recently and simplifies implementation is that swagger released own BOM since 2.2.47
swagger-api/swagger-core#4987
Having sprindoc version and swagger version in single springdoc BOM - single source of truth - will simplify springdoc incorporation in applications
PS.
I do not understand discussion under #3212:
- bnasslahsen on Feb 22:
You can add explicit swagger-core-jakarta dependency entry in your (project)
- bnasslahsen on Feb 23:
Adding this to the existing BOM would be a breaking change, as it would force users to specify the versions manually.
because locking swagger version in springdoc BOM will release users from specify the version manually (but let them freedom to change)
At concept level, there is nothing to add to #3212:
If springdoc declares supported swagger version in BOM, springdoc clients MAY import the BOM and be sure no conflict between springdoc and swagger
The only fact which happened recently and simplifies implementation is that swagger released own BOM since 2.2.47
swagger-api/swagger-core#4987
Having sprindoc version and swagger version in single springdoc BOM - single source of truth - will simplify springdoc incorporation in applications
PS.
I do not understand discussion under #3212:
because locking swagger version in springdoc BOM will release users from specify the version manually (but let them freedom to change)