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

Question: does the attachSwaggerArtifact not work anymore? #501

Closed
starJammer opened this issue Jul 8, 2017 · 3 comments
Closed

Question: does the attachSwaggerArtifact not work anymore? #501

starJammer opened this issue Jul 8, 2017 · 3 comments

Comments

@starJammer
Copy link

starJammer commented Jul 8, 2017

I tried adding attachSwaggerArtifact but it doesn't work. Where would I navigate to in order to get to this?

@azbarcea
Copy link

I use a pom.xml similar to the following, and I can confirm that attachSwaggerArtifact works as documented:
https://gist.github.com/azbarcea/05b55f0e660d1b4d335479cb602deb48

              <swaggerDirectory>${project.build.directory}/swagger-ui</swaggerDirectory>
              <!--
                  Do not use: swaggerFileName, as it will be used as classifier. 
                  In a multi-module project will have different classifier for different APIs
                -->
              <outputFormats>json</outputFormats>
              <attachSwaggerArtifact>true</attachSwaggerArtifact>

swagger-ui is going to be used as classifier, even if a ${project.build.directory}/swagger-ui (a longer path) is configured as swaggerDirectory

@dpursehouse
Copy link

I've found that if outputFormats is not set, contrary to what the documentation says it does not default to json and no json files are generated.

@starJammer
Copy link
Author

Thank you for the feedback guys. I'll try this but I ended up going in a different direction.

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

No branches or pull requests

3 participants