swagger-api / swagger-api/swagger-codegen
[JAVA] Understanding client deployment to maven repository
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
We use aws-maven and deploy all our maven libraries to S3 bucket. Would like to know what is the best way to deploy the generated java client to S3.
Swagger-codegen version
2.2.2
Command line used for generation
java -jar swagger-codegen-cli.jar generate -i target/generated/swagger.json -l java --library retrofit2 -o client/java -c config.json
Suggest a Fix
If pom.xml could have support for aws-maven plugin as a configurable option and if a distribution management is provided we could override the distribution repository from command line to deploy.
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 with the Java client output under client/java, config.json, and the generated pom.xml, then review the requested aws-maven deployment and distribution-management behavior. Done means the generated client can expose the requested repository configuration and support deployment to the S3-backed Maven repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- build-system, cloud, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100