On 17/05/2019 15:56, Julian Reschke wrote: > Given the time pressure, my proposal is to simply *backport* JCR-4429 to > Jackrabbit 2.18.x. It's just a set of new interfaces, after all, not > actually implemented by Jackrabbit. We'll then release 2.18.2, update > Oak trunk to use that, and are done.
+1 > > Going forward, we should however try to break this dependency. After > all, it's Oak which is driving the evolution of jackrabbit-api, so it > really should move over there. This will eliminate the top reason why we > have been branching Jackrabbit in the past. > > To do that, the following should work: > > - (svn) cp the subproject over to Oak, align the POM, but do not touch > package name or export versions > - once a new stable Oak is released (1.16, sometime later this year), > drop the jackrabbit-api subproject, and inside the other Jackrabbit > subprojects reference the new Oak artifact > - we probably should try to generate a "tombstone" release of > jackrabbit-api, that would point people to the changed location (needs > research...) before entirely removing the subproject +1. The tombstone release may easily be the latest stable we're just going to cut with the backport. If we don't introduce any API changes. Davide
