I am finding that due to multiple reasons, Jackson JSON Schema (v3) module is falling behind. One reason is that I have no personal use for it (or JSON Schema), and so there isn't much interest. Another one is that code came from contributions by developers who are not around (or active) any more. And third one is that codebase itself has some structural issues, so it is not necessarily easy to modify or reason about.
Anyway: on the other hand it seems that many developers find the module useful enough to report issues and contribute fixes, PRs, feature additions. This is great. At least as long as there is someone maintaining the module and doing same gatekeeping & mentoring to try to keep codebase as consistent as possible (given its state). At this point, alas, no such maintainer exists. So I am thinking of possibly deprecated this module in near future if this continues. Deprecation doesn't mean a lot on short term: addition of some verbiage on repo, addition of some disclaimed for issue tracker and so on. I will probably even keep on building new versions, at least for immediate future; and do whatever tweaks are necessary to keep it building and passing existing unit tests. -+ Tatu +- ps. Similar problems exist for `jackson-datatype-hibernate`; maintainers welcome! -- You received this message because you are subscribed to the Google Groups "jackson-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
