swagger-api / swagger-api/swagger-core

swagger-core depends on wrong artifacts

Open
#4,616 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backlog
Dominant language
Java
Stars
7.5k
Forks
2.3k
Avg merge
18h 1m
Merged PRs (30d)
10

Description

According to wiki, jakarta namespace is supported by dedicated artifacts, which means that swagger-core should depend on old (pre-jakarta) dependencies:

  1. jakarta.xml.bind-api -> jaxb-api (here)
  2. jakarta.validation-api -> validation-api (here)
  3. jakarta.ws.rs-api -> javax.ws.rs-api (here)
  4. jakarta.inject-api -> javax.inject (here)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the dependency entries in modules/swagger-core/pom.xml, using the linked wiki note and referenced lines as the starting point. Confirm that swagger-core uses the four pre-Jakarta artifacts listed in the issue, then verify the resulting dependency declarations and project build.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.