This repository has been archived by the owner on Jan 21, 2024. It is now read-only.
Use the latest jsonschema2pojo to fix an issue with schema names #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eam issue has been fixed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had an issue using the raml-jaxrs-codegen plugin that I traced down to the jsonschema2pojo creating the pojo with a name that didn't reflect what the rest of the code generation was expecting, so the generated code wouldn't compile.
There was a comment in the code about returning the actual generated type once joelittlejohn/jsonschema2pojo#137 was fixed - that issue has been fixed in 0.4.1 of org.jsonschema2pojo
This pull request uses that fixed version of jsonschema2pojo to fix the issue that I am experiencing.