Hi Andrei
The discussion wrt to making the upcoming release Oak 2.0 is not about
backwards compatibility (or making any kind of statement about this) but
rather to highlight the fact that we modularised Oak and by such allow us
to change the release model from all-in-one to independent releases of
Hi Ian
Sorry... I can't follow you here. Did I misunderstand your previous mail? I am
really curious why you felt that Jackrabbit API was not an option because I
don't recall that we had that option discussed in the lengthy thread that
preceded the contribution to oak-api.
Kind regards
Angela
Hi,
I have done some more thinking and coding overnight and now think the best
place for the API is in the Sling API, since thats were its used. This will
unblock Sling and allow Oak to choose, or not to implement the URIProvider
API.
I will adjust the Sling patch and discuss on sling-dev.
Best Re
Hi,
Moving URIProvider from Oak 1.6 oak-core (not yet patched) to JCR API would
require a patch to 2.14.2 with a new feature to make this API available to
Sling and Oak 1.6. I was told patching stable branches with new features
was not allowed in Oak. Only unstable branches can be patched with new
Hi
I am not sure it is the best place to ask a question but Oak does not have a
user mailing list.
I have to study a migration from Jackrabbit 2.X to Jackrabbit Oak.
At the moment I do not use OSGI.
Is this a good way to proceed?
I was able to use MongoDB and migrate nodes from 2.x (non-datast
The Apache Jenkins build system has built Jackrabbit Oak (build #885)
Status: Failure
Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/885/ to
view the results.
Changes:
[mduerig] OAK-6842: Refactor FileStore.close
Also leverage the closer for releasing the file store lock
Hello team,
I took the time to crunch in some dates and here's a proposal for our
next stable releases:
# 27th November
Branch and Release Jackrabbit 2.16.0
# 5th December
Update Oak 1.7.x to Jackrabbit 2.16.0. This will give us maximum
coverage on the usage of this specific version in Oak bas
Sounds good to me in general.
One thought however on...:
On 2017-10-18 12:12, Davide Giannella wrote:
Hello team,
I took the time to crunch in some dates and here's a proposal for our
next stable releases:
# 27th November
Branch and Release Jackrabbit 2.16.0
...
As we aren't doing any new
The Apache Jenkins build system has built Jackrabbit Oak (build #888)
Status: Failure
Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/888/ to
view the results.
Changes:
[reschke] OAK-6846: update maven-failsafe-plugin to 2.20.1
Test results:
All tests passed
