swagger-api / swagger-api/swagger-codegen
swagger codegen depends on non compatible apache 2.0 transitive library
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
swagger code gen ultimately depends on com.atlassian.com:base-pom:5.0.13 which is licensed under https://www.atlassian.com/legal/atlassian-customer-agreement and doesn't seem to be compatible with apache 2.0
Swagger-codegen version
3.0.54
Dependency Chain
swagger-codegen -> com.atlassian.commonmark:commonmark:0.17.0 -> com.atlassian.commonmark:commonmark-parent:0.17.0 -> com.atlassian.pom:central-pom:5.0.13 -> com.atlassian.pom:base-pom:5.0.13
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 inspecting swagger-codegen 3.0.54's dependency metadata and reproducing the reported chain from swagger-codegen through commonmark to the Atlassian POM artifacts. Determine how the transitive dependency can be removed or replaced, then verify the resolved dependency tree and licensing outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100