`dependencies` property should not be an Array but Object

[chriskessel]

The generated schema for my object creates this:

  "type": "object",
  "id": "urn:jsonschema:com:kessel:MyResponseObject",
  "dependencies": [],
  "patternProperties": {},
  ...

If I run that through the schema validator, it complains that dependencies should be an object, not an array. Looking at the v3 and v4 specs, they do call out this field as an object.

This is a bug in the schema generator? Or is there a spec addendum that I missed?

(A customer pointed out that our schema had this error and we use Jackson JsonSchema 2.7.0 to generate the schema).

[cowtowncoder]

@chriskessel Unfortunately I don't know enough about JSON Schema to really answer. This would be good to (try to) discuss on jackson-dev mailing list.

FWIW, this module works on v3 of JSON Schema spec, and it does not seem possible to create something that works on both. There exists a v4 module too (I don't have link handy but should be googlable).

[chriskessel]

FWIW, v3 and v4 have the same wording about the dependencies field being an object.

[cowtowncoder]

I don't doubt your statement, just pointing out that for any follow-up work, filing the issue itself probably won't lead to much changes.

[chriskessel]

Why? Is jackson jsonSchema a dead project?

[cowtowncoder]

@chriskessel I haven't seen anyone besides me reading issues here; and I did not write this module. I have tried to make occasional changes, but do not have use for JSON Schema myself (nor deep knowledge). There may be others interested in this module, but if so they are best reached via jackson mailing lists.

So this is not an active project by any means. It seems to be used quite widely, however.

[cowtowncoder]

Fixed as per merged #120; will be in 2.9.0.