Description
Is your feature request related to a problem? Please describe.
When using springdoc-openapi-ui, one gets a dependency to the old javax-apis through the version of swagger-core that is included (via springdoc-common).
Describe the solution you'd like
It seems swagger has solved this by publishing separate artifacts suffixed with jakarta (See swagger-api/swagger-core#3881). It would be nice if one could do the same with springdoc, or if possible solve it in some other way, so as not have to manually exclude the javax-swagger-versions and include the jakarta-swagger versions a la
implementation(
'io.swagger.core.v3:swagger-annotations-jakarta:2.1.11',
'io.swagger.core.v3:swagger-integration-jakarta:2.1.11',
'io.swagger.core.v3:swagger-models-jakarta:2.1.11'
)
implementation('org.springdoc:springdoc-openapi-ui:1.5.11') {
exclude(group: 'io.swagger.core.v3', module: 'swagger-annotations')
exclude(group: 'io.swagger.core.v3', module: 'swagger-integration')
exclude(group: 'io.swagger.core.v3', module: 'swagger-models')
}
I'm not well enough versed in all the possibilities of configuring dependencies in maven to come up with the best solution to this, but it would be nice if it could be solved somehow, as jakarta.* is where the development will continue.