You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you have parent contract e.g. Base.json in the root (e.g. /schema) and than you create the child contract Child.json (i.e. it uses extends) in sub-folder /schema/api, after plugin generation it will move parent's pojo near the child's pojo.
It never happens on Linux machine!
I found out the solution in your documentation - explicitly specify the order using <sourceSortOrder>FILES_FIRST</sourceSortOrder>
Why didn't you set up this as default value, but set up OS dependent behavior instead?
The text was updated successfully, but these errors were encountered:
search by "sourceSortOrder" get #719 and #1054 additional info
I don’t quite understand for what purposes sorting can be useful ... which cases?
example: class in parent extends class in subdirs and files in subdirs should be processed first?
files first works equals everywhere and without bugs
Link to the example with commented solution: https://github.com/oleggye/jsonschema2pojo-poc
When you have parent contract e.g.
Base.json
in the root (e.g./schema
) and than you create the child contractChild.json
(i.e. it usesextends
) in sub-folder/schema/api
, after plugin generation it will move parent's pojo near the child's pojo.It never happens on Linux machine!
I found out the solution in your documentation - explicitly specify the order using
<sourceSortOrder>FILES_FIRST</sourceSortOrder>
Why didn't you set up this as default value, but set up OS dependent behavior instead?
The text was updated successfully, but these errors were encountered: