On 15.06.2023 10:49, Julian Reschke wrote:
...
Potentially.
IIUC, the problem is partly caused by the fact that Oak has switched to
Java 11 in January, and Jackrabbit hasn't made that switch yet; thus
there is no Jackrabbit branch - in particular stable branch - that
implement Jackrabbit API changes made since.
If this is the problem, or part of the problem, it would help to:
- switch Jackrabbit trunk to Java 11, use the latest version of
Jackrabbit API, and start making stable releases from that, or
- backport these Jackrabbit API changes to Oak 1.22.*, so they would get
visible in Jackrabbit JDK world.
...JDK 8...
Best regards, Julian
