We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
ClientConfiguration
spring-cloud-security
spring-security-oauth2
The generated ClientConfiguration class always imports from spring-cloud-security and spring-security-oauth2 even if these imports are unused.
2.2.3
Example can be found at https://github.com/wjam/swagger-codegen-spring-cloud
Maven library used. Configuration is in the GitHub repo mentioned above
Remove the line **/ClientConfiguration.java from the .swagger-codegen-ignore file and run mvn clean compile
**/ClientConfiguration.java
.swagger-codegen-ignore
mvn clean compile
Only include those imports when they are actually required.
The text was updated successfully, but these errors were encountered:
same problem
Sorry, something went wrong.
only include imports which are actually required for spring-cloud Cli…
455fd3d
…entConfiguration generator (closes swagger-api#6683)
037bccc
Might be a little late for the party, but I created a pull request for this issue.
Successfully merging a pull request may close this issue.
Description
The generated
ClientConfiguration
class always imports fromspring-cloud-security
andspring-security-oauth2
even if these imports are unused.Swagger-codegen version
2.2.3
Swagger declaration file content or url
Example can be found at https://github.com/wjam/swagger-codegen-spring-cloud
Command line used for generation
Maven library used. Configuration is in the GitHub repo mentioned above
Steps to reproduce
Remove the line
**/ClientConfiguration.java
from the.swagger-codegen-ignore
file and runmvn clean compile
Suggest a fix/enhancement
Only include those imports when they are actually required.
The text was updated successfully, but these errors were encountered: