Hi,
In a recent post, I was shown that in my jax-rs-CXF-Maven application being migrated to the new Swagger-Core (1.5.0), my list of dependencies was not complete compared to the example application. What is interesting about this is that in the 1.3.0 version, all the dependencies downloaded perfectly and Swagger performed the scan and I was able to build the app and deploy it it Tomcat and hit api-docs. In a previous exchange of emails, it was stated that all I had to do was replace com.wordnik.swagger with io.swagger and it would all work, but that is not the case.
Because it was pointed out to me that my pom.xml file must be the issue because of the lack of necessary dependencies in my mvn clean:tree, I painstakingly examined all the Maven logs and added all the missing dependencies. Every dependency that was include in the mvn clean-tree from the example application I included in the pom.xml file to comply. What is strange is the breadth of what needed to be added. I had to manually add swagger-annotations, com.fasterxml.jackson.jaxrs, org.reflections, com.fasterxml.jackson.dataformat, com.fasterxml.jackson.datatype, com.fastercaml.jackson.jaxrs. And, Maven could still not build the application because it had an issue with the <proper scan=true> property. So, I commented this out and Maven will build and the application can be deployed.
I am confused as to how it is that I can include every single dependency that it was suggested I needed, had to manually include them, and still can't generate a swagger. json file. Clearly, my project is not messed up because Swagger 1.3.0 worked fine, with the common 1.3.0 bugs that I was upgrading to get rid of. I remain suspicious of the Swagger-Core file I am using, especially when Maven could not understand the scan property. To test this methodically, again, could you please provide the version number of the Swagger-Core file I should be using for jaxrs-cxf-maven-java. The versioning and platforms are confusing to me. I would appreciate it if you could direct me to the specific maven url to get this jar.
Thanks,
johnh