swagger-api/swagger-codegen

[JAVA] Understanding client deployment to maven repository

Open

#5796 opened on Jun 7, 2017

View on GitHub
 (3 comments) (0 reactions) (0 assignees)HTML (12,701 stars) (5,474 forks)batch import
Client: JavaEnhancement: Generalhelp wanted

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

Tech stack
java
Domain
devopsbuild system
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaMavenunderstanding of pom.xml
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the current pom.xml in the swagger codegen project to understand how Maven plugins are configured. Research the aws maven plugin and its integration. Check if there have been any recent changes or related PRs that address this feature. Propose a configuration option to enable the aws maven plugin and allow S3 deployment.