Jackrabbit OCM is unmaintained, there has been no activity on the project since 11 years.

For backwards compatibility we currently maintain out own fork. Going forward we should however replace it with a more sustainable solution.

We need to carefully consider backwards compatibility though. OCM comes with annotations that we expose to our customers. So for 6.2 we cannot just remove them. For 6.3 we need to think of a migration path. So I think it makes sense to still have OCM around (but deprecate it) while at the same time providing a new solution.

A while ago mgeljic started drafting a solution.