jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Reschke <julian.resc...@gmx.de>
Subject Re: changed Jackrabbit API for JCR-4429 and upcoming stable Oak release
Date Thu, 13 Jun 2019 10:06:34 GMT
On 22.05.2019 17:19, Julian Reschke wrote:
> ...
>>> 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.
>
> Now tracked in <https://issues.apache.org/jira/browse/OAK-8339>.
> ...

FYI: the changes on the Oak side have now been done.

Best regards, Julian

Mime
View raw message