-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
"Path not present" error when processing multiple JSON files having objects with the same name #1427
Comments
unkish
added a commit
to unkish/jsonschema2pojo
that referenced
this issue
Jan 18, 2023
…ON/YAML source inputs Closes joelittlejohn#1427
unkish
added a commit
to unkish/jsonschema2pojo
that referenced
this issue
Jan 22, 2023
…ON/YAML source inputs Closes joelittlejohn#1427
unkish
added a commit
to unkish/jsonschema2pojo
that referenced
this issue
Jan 26, 2023
…ON/YAML source inputs Closes joelittlejohn#1427
joelittlejohn
changed the title
jsonschema2pojo 1.1.2 fails with "Path not present: watcher" error when processing multiple json files having objects with the same name
"Path not present" error when processing multiple JSON files having objects with the same name
Jan 26, 2023
unkish
added a commit
to unkish/jsonschema2pojo
that referenced
this issue
Feb 15, 2023
…ON/YAML source inputs Closes joelittlejohn#1427
joelittlejohn
added a commit
that referenced
this issue
Feb 15, 2023
When using JSON or YAML files (not schemas, but example data) the schemas will not have a proper file path in their ID, as there is no actual schema file. All schema IDs will be fragments only (relative references within the document). Once generation is complete for a file, these schemas should be thrown away and not reused. Closes #1427
joelittlejohn
added a commit
that referenced
this issue
Feb 16, 2023
When using JSON or YAML files (not schemas, but example data) the schemas will not have a proper file path in their ID, as there is no actual schema file. All schema IDs will be fragments only (relative references within the document). Once generation is complete for a file, these schemas should be thrown away and not reused. Closes #1427
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
jsonschema2pojo 1.1.2 fails with "Path not present: watcher" error when processing multiple json files having objects with the same name, e.g.:
... and the following configuration:
The error persists if I move json-files into different subdirectories of "sourceDirectory". I expect that json-files in different subdirectories will result in POJOs with different packages to avoid naming conflicts.
The text was updated successfully, but these errors were encountered: