Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O openapi-generator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,476
    • Issues 3,476
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 402
    • Merge requests 402
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenAPI Tools
  • openapi-generator
  • Merge requests
  • !9434

Could org.openapitools:petstore-resteasy:1.0.0 drop off redundant dependencies to loose weight?

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Administrator requested to merge github/fork/Celebrate-future/master into master May 09, 2021
  • Overview 0
  • Commits 1
  • Pipelines 0
  • Changes 1

Created by: Celebrate-future

Hi, I am a user of project org.openapitools:petstore-resteasy:1.0.0. I found that its pom file introduced 43 dependencies. However, among them, 11 libraries (25%) have not been used by your project (the redundant dependencies are listed below). Reduce these useless dependencies can help prevent conflicts between library versions. MeanWhile, it can minimize the total added size to projects. It can also help enable advanced scenarios for users of your package. This PR helps org.openapitools:petstore-resteasy:1.0.0 lose weight :) I have tested the revised configuration in my local environment. It is safe to remove the unused libraries.

Best regards

Redundant dependencies----


javax.xml.bind:jaxb-api:jar:2.2.7:compile
net.jcip:jcip-annotations:jar:1.0:compile
com.sun.mail:javax.mail:jar:1.5.6:compile
com.sun.istack:istack-commons-runtime:jar:2.16:compile
com.sun.xml.bind:jaxb-impl:jar:2.2.7:compile
javax.xml.bind:jsr173_api:jar:1.0:compile
com.sun.xml.fastinfoset:FastInfoset:jar:1.2.12:compile
javax.activation:activation:jar:1.1.1:compile
com.sun.xml.bind:jaxb-core:jar:2.2.7:compile
org.jboss.resteasy:resteasy-jaxrs-services:jar:3.1.3.Final:compile
org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:1.0.0.Final:compile

PR checklist

  • Read the contribution guidelines.
  • Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
  • Run the following to build the project and update samples:
    ./mvnw clean package 
    ./bin/generate-samples.sh
    ./bin/utils/export_docs_generators.sh
    Commit all changed files. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH.
  • File the PR against the correct branch: master, 5.1.x, 6.0.x
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request. @bbdouglas (2017/07) @sreeshas (2017/08) @jfiala (2017/08)
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/Celebrate-future/master