[Oak origin/trunk] Apache Jackrabbit Oak matrix - Build # 750 - Still Failing

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #750) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/750/ to view the results. Changes: [davide] OAK-3996 - Update Jackrabbit version to 2.12.0

Re: DocumentStore question.

Hi, On 12/02/16 17:11, "ianbos...@gmail.com on behalf of Ian Boston" wrote: >Is there an assumption that the revisions listed in _revisions are >ordered ? There is no requirement that entries in _revisions map are ordered at the storage layer, but the DocumentStore will order them when it reads

Re: oak-upgrade test failures (was Re: Oak 1.3.16 release plan)

Hi Tomek, Thx a lot. I'll patch the relevant branches now. Best regards, Manfred On 2/15/2016 11:41 AM, Tomek Rekawek wrote: Hello, The already mentioned JCR-2633 puts jcr:mixinTypes property into NodePropBundle#getPropertyEntries(). As a result, the oak-upgrade code responsible for

Re: OAK-4006 : Enable cloning of repo for shared data store and discovery-lite

Thanks for the various comments and review on OAK-4006. I've attached a final version of the patch and will push that later this afternoon (together with OAK-4007) unless I hear fresh concern. Cheers, Stefan On 11/02/16 20:16, "Stefan Egli" wrote: >Hi all, > >The recent

Re: oak-upgrade test failures (was Re: Oak 1.3.16 release plan)

On 15/02/2016 10:47, Julian Reschke wrote: > ...in the meantime, I think we should change oak-trunk back to use > 2.11.3, so we have a clean build until this new issue is understood > and fixed. Done! :) Cheers Davide

Re: oak-upgrade test failures (was Re: Oak 1.3.16 release plan)

On 2016-02-15 11:47, Julian Reschke wrote: ...in the meantime, I think we should change oak-trunk back to use 2.11.3, so we have a clean build until this new issue is understood and fixed. Best regards, Julian Related to that...: OAK 1.2 currently uses Jackrabbit 2.10.0, although 2.10.1 has

Re: oak-upgrade test failures (was Re: Oak 1.3.16 release plan)

On 2016-02-15 10:31, Davide Giannella wrote: On 12/02/2016 18:36, Manfred Baedke wrote: Hi, This is due to change 1721196 (associated with JCR-2633), which changes the persistent data model. Probably the test has just to be tweaked accordingly, I'll look into it during WE. Thank you very much

Re: oak-upgrade test failures (was Re: Oak 1.3.16 release plan)

Hello, The already mentioned JCR-2633 puts jcr:mixinTypes property into NodePropBundle#getPropertyEntries(). As a result, the oak-upgrade code responsible for replacing mix:simpleVersionable with mix:versionable doesn’t work correctly (the results are replaced by the original properties). I

Re: oak-upgrade test failures (was Re: Oak 1.3.16 release plan)

The test failures in the issue seem to suggest that this may be relates to simple versionables. IIRC we recently added support for some broken JR2 constructs. Could they have been fixed in the last JR release? If that's the case it may no longer be possible to populate the source repository for

Re: Anchor tags on doc pages get positioned wrongly under top menu

On 14/02/2016 17:42, Julian Sedding wrote: > Hi Vikas > > I agree that having the anchor text hidden is a usability hazard. I > tried your suggested approach in Firefox (via FireBug) and didn't have > any success. However, a slight variation of the scheme, still relying > on the ":target" pseudo

Re: oak-upgrade test failures (was Re: Oak 1.3.16 release plan)

On 12/02/2016 18:36, Manfred Baedke wrote: > Hi, > > This is due to change 1721196 (associated with JCR-2633), which > changes the persistent data model. Probably the test has just to be > tweaked accordingly, I'll look into it during WE. Thank you very much Manfred. I've filed