Generated code uses deprecated Json4JProvidersRegistry

[danlz]

The generated Application class uses the deprecated Json4JProvidersRegistry class.

[berezovskyi]

Unfortunately, some tools like IBM Jazz still actively rely on this non-standard format that we marked as unsupported. For user convenience, we are still generating the code to enable support for that format. However, the project will only be supporting W3C JSON-LD over non-standard "OSLC JSON". If you find a high-impact bug in the non-standard "OSLC JSON" providers, we might still merge the fix for that considering what I described above, but no new feature development is planned.

[berezovskyi]

Please reopen if this doesn't resolve the issue for you.

[jadelkhoury]

@berezovskyi ! Given that, how about no longer marking Json4JProvidersRegistry as deprecated?
Is it just the registry that is deprecated, or the whole json-provider library?

[berezovskyi]

@jadelkhoury I think you can get away with RDF/XML with Jazz. I would be happy to remove OSLC JSON support once we confirm that, actually.

[danlz]

Maybe this can be controlled through some parameter?

[berezovskyi]

Ideally, yes

[berezovskyi]

Update: OSLC doesn't require OSLC JSON but some domain specs like OSLC RM do: eclipse-lyo/lyo.testsuite#29 (comment)