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

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #857) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/857/ to view the results. Changes: [catholicon] OAK-4299: oak-run console should connect to reposi

[Oak origin/1.4] Apache Jackrabbit Oak matrix - Build # 856 - Still Failing

The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build #856) Status: Still Failing Check console output at https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/856/ to view the results. Changes: [alexparvulescu] OAK-4306 Disable cleanup when compaction is pa

Re: [VOTE] Please vote for the final name of oak-segment-next

hi michael in general i would prefer a name containing -segment- exceptions: those names ending with a version hint or -next, which looks quite troublesome to me... in particular as we plan to to retire the original segment nodestore impl (or even move it to the archive altogether). kind regards

Re: [VOTE] Please vote for the final name of oak-segment-next

Hi, my vote in order of preference: +1 oak-segment-tar +1 oak-segment-file +1 oak-segment-store alex On Mon, Apr 25, 2016 at 4:46 PM, Michael Dürig wrote: > > Hi, > > There is a couple of names that came up in the discussion [1]: > > oak-local-store > oak-segment-file > oak-embedded-s

Re: [VOTE] Please vote for the final name of oak-segment-next

oak-segment-file +1 oak-segment-store +1 oak-segment-tar +1 Michael On 25.4.16 4:52 , Vikas Saurabh wrote: oak-embedded-store +1 Thanks, Vikas

Re: [VOTE] Please vote for the final name of oak-segment-next

Hi +1 for oak-segment-file or oak-segment-tar. +0 for oak-segment-store. We *may* implement another segment-based persistence later, in which case having the persistence strategy in the name sounds like a good idea to me. Similarly, a later refactoring of the document store could lead to oak-doc

Re: [VOTE] Please vote for the final name of oak-segment-next

+1 to oak-segment-store. 2016-04-26 14:04 GMT+02:00 Stefan Egli : > Hi, > > On 26/04/16 14:00, "Thomas Mueller" wrote: > > >I would keep the "oak-segment-*" name, so that it's clear what it is based > >on. So: > > > >-1 oak-local-store > >-1 oak-embedded-store > > > >+1 oak-segment-* > > > >With

Re: [VOTE] Please vote for the final name of oak-segment-next

Hi, On 26/04/16 14:00, "Thomas Mueller" wrote: >I would keep the "oak-segment-*" name, so that it's clear what it is based >on. So: > >-1 oak-local-store >-1 oak-embedded-store > >+1 oak-segment-* > >Within the oak-segment-* options, I don't have a preference. +1 (I do like 'oak-segment-v2' th

Re: [VOTE] Please vote for the final name of oak-segment-next

Hi, I would keep the "oak-segment-*" name, so that it's clear what it is based on. So: -1 oak-local-store -1 oak-embedded-store +1 oak-segment-* Within the oak-segment-* options, I don't have a preference. Regards, Thomas On 25/04/16 16:46, "Michael Dürig" wrote: > >Hi, > >There is a coupl

Re: Oak 1.4.2 release plan

Hi Davide, there's a small problem with the rollback, the 'oak-webapp' project now depends on a 'future' version of Oak (1.4.3-SNAPSHOT), so the build fails locally for me. best, alex [0] https://github.com/apache/jackrabbit-oak/blob/1.4/oak-examples/webapp/pom.xml#L38 On Mon, Apr 25, 2016 at

Re: [VOTE] Please vote for the final name of oak-segment-next

Missed sending nomination on earlier thread. If not late then one more proposal oak-segment-v2 This is somewhat similar to names used in Mongo mmapv1 and mmapv2. Chetan Mehrotra On Tue, Apr 26, 2016 at 2:32 PM, Tommaso Teofili wrote: > oak-segment-store +1 > > Regards, > Tommaso > > Il giorno

Re: [VOTE] Please vote for the final name of oak-segment-next

oak-segment-store +1 Regards, Tommaso Il giorno lun 25 apr 2016 alle ore 16:52 Vikas Saurabh < vikas.saur...@gmail.com> ha scritto: > > oak-embedded-store +1 > > > Thanks, > Vikas >