Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REQ] [Java] Swagger dependency old #5478

Open
dummyalias opened this issue Feb 28, 2020 · 3 comments
Open

[REQ] [Java] Swagger dependency old #5478

dummyalias opened this issue Feb 28, 2020 · 3 comments

Comments

@dummyalias
Copy link

Is your feature request related to a problem? Please describe.

Through this issue I'm forced to use different Swagger versions in my project, which leads to more dependencies and more knowledge, that developers at my company have to acquire about the different Swagger versions.

Describe the solution you'd like

In my pom.xml I want to have this:

        <dependency>
            <groupId>io.swagger</groupId>
            <artifactId>swagger-annotations</artifactId>
            <version>2.1.1</version>
        </dependency>

Describe alternatives you've considered

I considered manually changing my templates, but that doesn't seem to work, because the old imports are written using the {{#imports}}...{{/imports}} variable.

If the pain of using two different Swagger versions in parallel in my project becomes too high, I will reluctantly consider turning off the automatic code generation and "manually" update.

Additional context

There is already #4245, #5388 and #4779 for the spring generator and #27 for the jaxrs-* generators.

@InfoSec812
Copy link
Contributor

This is also related to the work being done for #5803 and #6108 ... We should all coordinate efforts to make this work for all Java implementations properly. I guess that my question becomes "Do we need to maintain support for the older Swagger 2 annotations or should we move completely to Swagger3/OAS?"

@TehBakker
Copy link

Any news on that?
This prevents me from using openPai plugins requiring the right annotation, there is no reason to use the old atm.
A property to allow to use old one might be good, but the default implementation should be the right annotations

@nikosmoum
Copy link

Any updates on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants