swagger-api / swagger-api/swagger-core
Consider upgrading jakarta.xml.bind-api to 4.x
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 7.5k
- Forks
- 2.3k
- Avg merge
- 18h 1m
- Merged PRs (30d)
- 10
Description
Currently, the project "swagger-core-jakarta" depends on "jakarta.xml.bind:jakarta.xml.bind-api:3.0.0" which depends on
"com.sun.activation:jakarta.activation:2.0.0".
Latest version of jakarta.xml.bind-api is 4.0.0 which depends on the new module from jakarta:
jakarta.activation:jakarta.activation-api:2.1.2.
Spring Framework (org.springframework.boot:spring-boot-starter-mail:3.1.5) via (org.eclipse.angus:jakarta.mail:1.1.0) uses the new activation libraries.
Having both on the classpath causes incompatibility issues between the 2 libraries.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the dependency declarations for the swagger-core-jakarta project and inspect how jakarta.xml.bind-api 3.0.0 and its activation dependency are introduced. Update the declaration to the requested 4.x line, then verify dependency resolution no longer brings incompatible activation libraries onto the classpath.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100