Re: trunk build failing

... and a sample of a failing test: testRestoreChild1(org.apache.jackrabbit.test.api.version.RestoreTest) Time elapsed: 0.019 sec <<< ERROR! javax.jcr.RepositoryException: org.apache.jackrabbit.oak.api.CommitFailedException: OakConstraint0022:

Jackrabbit-trunk - Build # 2328 - Still Failing

The Apache Jenkins build system has built Jackrabbit-trunk (build #2328) Status: Still Failing Check console output at https://builds.apache.org/job/Jackrabbit-trunk/2328/ to view the results.

[jira] [Updated] (JCR-3914) Support default aws region

[ https://issues.apache.org/jira/browse/JCR-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated JCR-3914: -- Fix Version/s: (was: 2.11.2) 2.11.3 > Support default aws region >

Re: Why does oak-core import every package with an optional resolution?

Looking at history of oak-core/pom.xml this change was done in [1] for OAK-1708 most like to support loading of various DB drivers from within Oak Core and probably a temp change which was not looked back again. That might not be required now as the DataSource gets injected and oak-core need not

Re: Why does oak-core import every package with an optional resolution?

A friendly reminder of this issue. Is there a specific reason why every dependency in oak-core has an optional resolution? 2015-10-22 15:34 GMT+02:00 Francesco Mari : > Hi, > > can somebody explain me why oak-core has the "Import-Package" > directive set to

trunk build failing

Hi, the trunk IT build is failing, could someone please take a look? Tests in error: testRestoreChild1(org.apache.jackrabbit.test.api.version.RestoreTest): org.apache.jackrabbit.oak.api.CommitFailedException: OakConstraint0022: /testroot/versionableNodeName1/child1[[test:versionable]]:

Re: trunk build failing

Cool, created OAK-3551. this will probably affect the pending 1.3.9 release. On Mon, Oct 26, 2015 at 12:18 PM, Angela Schreiber wrote: > hi alex > > that might be related to OAK-3541. i committed an initial fix because > the issue completely blocked me... though OAK-3541 is

[jira] [Updated] (JCR-3913) Test failures: NodeLocalNameTest

[ https://issues.apache.org/jira/browse/JCR-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated JCR-3913: -- Fix Version/s: (was: 2.11.2) 2.11.3 > Test failures: NodeLocalNameTest >

[jira] [Updated] (JCR-3901) TCK LockManagerTest does not allow new JCR 2.0 for lock token transfers

[ https://issues.apache.org/jira/browse/JCR-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated JCR-3901: -- Fix Version/s: (was: 2.11.2) 2.11.3 > TCK LockManagerTest does not allow

Re: trunk build failing

hi alex that might be related to OAK-3541. i committed an initial fix because the issue completely blocked me... though OAK-3541 is rather located in the version storage it might now reveal other bugs we didn't spot up to now. can you create another issue and link it to OAK-3541? i planned to

[jira] [Updated] (JCR-3924) Allow release-deploy to skip tests

[ https://issues.apache.org/jira/browse/JCR-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated JCR-3924: -- Fix Version/s: 2.11.3 > Allow release-deploy to skip tests > -- >

[jira] [Created] (JCR-3924) Allow release-deploy to skip tests

Davide Giannella created JCR-3924: - Summary: Allow release-deploy to skip tests Key: JCR-3924 URL: https://issues.apache.org/jira/browse/JCR-3924 Project: Jackrabbit Content Repository Issue

[jira] [Updated] (JCR-3924) Allow release-deploy to skip tests

[ https://issues.apache.org/jira/browse/JCR-3924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated JCR-3924: -- Priority: Blocker (was: Major) > Allow release-deploy to skip tests >

Start multiple instances of Oak throws an CommitFailedException

Hi everyone, I'm working on a project where we need to deploy multiple instances of Oak pointing to the same MongoDB. The problem is that sometimes in the initialization phase (initialize method of OakInitializer class) a CommitFailedException happens and what I understood of why this happens

jackrabbit-oak build #6693: Broken

Build Update for apache/jackrabbit-oak - Build: #6693 Status: Broken Duration: seconds Commit: 4dc39f3c0316bc5ed1b9213fe787ed02f4f87779 (1.0) Author: Alexandru Parvulescu Message: OAK-3409 CompositeRegistration.unregister diagnostics not helpful - merged

jackrabbit-oak build #6692: Broken

Build Update for apache/jackrabbit-oak - Build: #6692 Status: Broken Duration: seconds Commit: a1dd2309188e518edf98ca78ff9e9d110942d66e (1.2) Author: Alexandru Parvulescu Message: OAK-3409 CompositeRegistration.unregister diagnostics not helpful - merged

jackrabbit-oak build #6694: Fixed

Build Update for apache/jackrabbit-oak - Build: #6694 Status: Fixed Duration: seconds Commit: 799b8bb4f51564430bd69bca6f1635f8c150b6e5 (trunk) Author: Marcel Reutegger Message: OAK-3551: Failing version restore tests git-svn-id:

[jira] [Commented] (JCRSITE-44) Update contributor list

[ https://issues.apache.org/jira/browse/JCRSITE-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14975251#comment-14975251 ] Tae commented on JCRSITE-44: Stefan Egli is missing in the committer list. His Apache ID is stefanegli. And

[jira] [Created] (JCR-3925) JCR_SQL2 returns duplicated rows

Kamil created JCR-3925: -- Summary: JCR_SQL2 returns duplicated rows Key: JCR-3925 URL: https://issues.apache.org/jira/browse/JCR-3925 Project: Jackrabbit Content Repository Issue Type: Bug

Re: Using Jackrabbit Oak with MongoDB java driver v3

Hi, Oak does not use any MongoDB 3.x features at the moment, which means there was not need to upgrade the driver to 3.x so far. The driver version used in trunk and on the 1.2 branch in Oak is 2.13.x. This driver version is compatible with MongoDB 3.x and you can use Oak in this combination. As

Re: Why does oak-core import every package with an optional resolution?

On 2015-10-26 12:13, Chetan Mehrotra wrote: Looking at history of oak-core/pom.xml this change was done in [1] for OAK-1708 most like to support loading of various DB drivers from within Oak Core and probably a temp change which was not looked back again. That might not be required now as the

[VOTE] Release Apache Jackrabbit 2.11.2

A candidate for the Jackrabbit 2.11.2 release is available at: https://dist.apache.org/repos/dist/dev/jackrabbit/2.11.2/ The release candidate is a zip archive of the sources in: https://svn.apache.org/repos/asf/jackrabbit/tags/2.11.2/ The SHA1 checksum of the archive is

jackrabbit-oak build #6688: Fixed

Build Update for apache/jackrabbit-oak - Build: #6688 Status: Fixed Duration: seconds Commit: 83dced765bc776a709eac54fc87f9cf6c9ac7491 (1.2) Author: Alexandru Parvulescu Message: OAK-3546 Improve ObservationManagerImpl timeout message - merged r1710614

Re: Why does oak-core import every package with an optional resolution?

On 2015-10-26 16:37, Francesco Mari wrote: 2015-10-26 13:15 GMT+01:00 Julian Reschke : On 2015-10-26 12:13, Chetan Mehrotra wrote: Looking at history of oak-core/pom.xml this change was done in [1] for OAK-1708 most like to support loading of various DB drivers from