Re: [CompositeDataStore] How to properly create delegate data stores?

Hi Tomek, Thanks for the clarification. I’ve been working on applying the feedback you provided, studying CompositeNodeStore for guidance, etc. One question inline below. On October 4, 2017 at 1:22:22 AM, Tomek Rękawek (tom...@apache.org) wrote: As above, the CompositeDataStore won’t wait

BUILD FAILURE: Jackrabbit Oak (ManyChildNodesIT) - Build # 4 - Still Failing (ManyChildNodesIT)

The Apache Jenkins build system has built Jackrabbit Oak (ManyChildNodesIT) (build #4) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak%20(ManyChildNodesIT)/4/ to view the results. Changes: No changes Test results: No tests ran.

BUILD FAILURE: Jackrabbit Oak (ManyChildNodesIT) - Build # 3 - Still Failing (ManyChildNodesIT)

The Apache Jenkins build system has built Jackrabbit Oak (ManyChildNodesIT) (build #3) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak%20(ManyChildNodesIT)/3/ to view the results. Changes: No changes Test results: No tests ran.

BUILD FAILURE: Jackrabbit Oak (ManyChildNodesIT) - Build # 2 - Still Failing (ManyChildNodesIT)

The Apache Jenkins build system has built Jackrabbit Oak (ManyChildNodesIT) (build #2) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak%20(ManyChildNodesIT)/2/ to view the results. Changes: [reschke] OAK-6852: RDBDocumentStore conditional remove:

BUILD FAILURE: Jackrabbit Oak - Build # 897 - Still Failing

The Apache Jenkins build system has built Jackrabbit Oak (build #897) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/897/ to view the results. Changes: [reschke] OAK-6852: RDBDocumentStore conditional remove: check condition properly [reschke]

BUILD FAILURE: Jackrabbit Oak (ManyChildNodesIT) - Build # 1 - Failure (ManyChildNodesIT)

The Apache Jenkins build system has built Jackrabbit Oak (ManyChildNodesIT) (build #1) Status: Failure Check console output at https://builds.apache.org/job/Jackrabbit%20Oak%20(ManyChildNodesIT)/1/ to view the results. Changes: No changes Test results: No tests ran.

[jira] [Updated] (JCR-4134) update build instructions wrt Java versions

[ https://issues.apache.org/jira/browse/JCR-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4134: Fix Version/s: 2.16 > update build instructions wrt Java versions >

[jira] [Updated] (JCR-4104) cleanup how command lines for test executions are constructed

[ https://issues.apache.org/jira/browse/JCR-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4104: Fix Version/s: 2.16 > cleanup how command lines for test executions are constructed >

[jira] [Updated] (JCR-4121) ConcurrentModificationException in InternalVersionHistoryImpl.fixLegacy()

[ https://issues.apache.org/jira/browse/JCR-4121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4121: Fix Version/s: 2.16 > ConcurrentModificationException in InternalVersionHistoryImpl.fixLegacy() >

[jira] [Updated] (JCR-4106) fix JCR API docs link

[ https://issues.apache.org/jira/browse/JCR-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4106: Fix Version/s: 2.16 > fix JCR API docs link > - > > Key: JCR-4106

[jira] [Updated] (JCR-4107) Upgrade to httpclient 4.5.3

[ https://issues.apache.org/jira/browse/JCR-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4107: Fix Version/s: 2.16 > Upgrade to httpclient 4.5.3 > --- > >

Re: Oak 1.7.10 release plan

Hi, Amit has resolved the issue. 1.7.10 is no longer blocked. Best Regards Ian On 20 October 2017 at 09:57, Davide Giannella wrote: > On 19/10/2017 16:57, Ian Boston wrote: > > Are you able to revert the 3 commits listed in the issue ? > > If thats done, you can resolve the

Re: Oak 1.7.10 release plan

On 19/10/2017 16:57, Ian Boston wrote: > Are you able to revert the 3 commits listed in the issue ? > If thats done, you can resolve the issue. > Nothing else depends on these changes at this time, and should not, hence > the blocker. Technically yes. However I'm not confident in doing it as I

BUILD FAILURE: Jackrabbit Oak - Build # 896 - Failure

The Apache Jenkins build system has built Jackrabbit Oak (build #896) Status: Failure Check console output at https://builds.apache.org/job/Jackrabbit%20Oak/896/ to view the results. Changes: [chetanm] OAK-6849 - Avoid creating empty properties node under indexRules [amitj] OAK-6841: Revert

[jira] [Commented] (JCRVLT-216) Aggregate defined children of the filter path ancestors, optionally install them

[ https://issues.apache.org/jira/browse/JCRVLT-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16212304#comment-16212304 ] Nicolas Peltier commented on JCRVLT-216: I agree on a general case that this is not a good

Jackrabbit 2.15.7 Release Plan

Hi, I'd like to cut Jackrabbit 2.15.7 early next week. Note that this could be the last unstable release before we branch for 2.16. The list of open issues scheduled for 2.15.7 is empty:

[jira] [Created] (JCR-4201) Release Jackrabbit 2.15.7

Julian Reschke created JCR-4201: --- Summary: Release Jackrabbit 2.15.7 Key: JCR-4201 URL: https://issues.apache.org/jira/browse/JCR-4201 Project: Jackrabbit Content Repository Issue Type: Task