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
[Java] Cannot build code generated by Maven plugin #4298
Comments
Aha - the clue is in
If you want to keep this as the default (I prefer Jackson / Jersey, but that's just my little opinion), then the maven codegen examples need to be updated, and the documentation should tell me how I can now invoke what used to be the default option (is that |
OK - I managed to resolve this looking through the code and provided the above pull request to update the documentation. Hope that helps! |
I recently updated from 2.1.6 to 2.2.1 as i needed the new "templateDirectory" feature that works in 2.2.1. but as soon as i did that i get same complier errors. how did you resolve this? help! |
is there a way to still use jersy and ignore the new default GSON library? |
@aparnarus: use the |
Thank you! im not sure how i missed it - but yes that worked. |
it solved for me many thanks |
Description
I'm using the Maven plugin to generate Java code. Following the generation, I get errors compiling the generated code such as:
I'm surprised because I expect Jersey client 1.18. JSON processing: Jackson 2.4.2 to be used, as documented in the readme - why do I need GSON or OKIO. If I do, I can't find which dependencies I would need to add to resolve this issue - I am using the examples in the swagger-maven-plugin documentation, but the build is still failing
Swagger-codegen version
2.2.1 - it was working in 2.1.6
Swagger declaration file content or url
https://github.com/amadeus-travel-innovation-sandbox/sandbox-content/blob/master/swagger.yml
Command line used for generation
Codegen config
Dependencies and properties
Steps to reproduce
Clone and build https://github.com/tadhgpearson/swagger-maven-plugin-dependencies
I'm using Java 8 & Maven 3.3
Related issues
Perhaps #3261 ?
Suggest a Fix
Behaviour suggests the default is now using GSON + OK HTTP - maybe that's where the bug is?
The text was updated successfully, but these errors were encountered: