On 03.05.2019 13:11, Davide Giannella wrote:
On 03/05/2019 10:35, Angela Schreiber wrote:
hi oak-devs
for my recent work on OAK-8190 i would need the latest jackrabbit-api including
the extension added with JCR-4429. looking that summary written by Davide
recently (http://markmail.org/message/bndcm5jwfasj4otm) and on the oak
documentation i couldn't find if we are still fine to temporarily have a
snapshot dependency to jackrabbit during development. i vaguely remember that
we discussed this topic but don't recall the final conclusion/decision.
i already create a task reminding us that we need to update the jackrabbit
version in the parent pom (https://issues.apache.org/jira/browse/OAK-8295)
before cutting 1.14.0 but obviously that's a bit late for the ongoing
development.
No SNAPSHOT please. Release an unstable JR and include such version oak
trunk. We will then decide whether release a new stable or backport. The
non-snapshot will ease the integration for downstream projects.
+1
Davide
PS: yes we should discuss what we're going to do with JR but in short I
think it makes sense for now to adopt the same model we're using for Oak.
Given the small amount of changes in Jackrabbit, I would expect that we
can just backport the API changes to 2.18.* when we need a stable release.
That said, do we know *when* that will be the case?
Best regards, Julian
