MODLD-602: Updated TitleFieldRequest & TitleFieldResponse to avoid oneOf at the top level #57
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.
Problem:
When
oneOf
is at the top level (as in TitleFieldRequest.json), then you have to give the full path inref
element in line 10, 21 & 32. If relative path is used, maven openapi plugin will fail. This problem do not occur ifallOf
is in the top level as in this file. So, I believe it is a bug in the plugin.However, if you give full path, then the python script used by jenkins to generate api-doc will fail with error
Error: Invalid JSON pointer: schema/resource/common/title/PrimaryTitle.json
. See this failed build (build is shown Green even though it actually failed). Expand "Do api-doc" to see the failure.Fix given in this ticket:
I rearranged the JSON schemas so that "oneOf" element do not appear in the top level. This way, we can give relative paths in "$ref" element. This will make the python script &
mvn clean install
pass. See this java doc generation using this branch.