The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.5.11 The release is available for download at:
http://jackrabbit.apache.org/downloads.html
See the full release notes below for details about this release:
Release Notes -- Apache Jackrabbit Oak --
Hi all,
Tomorrow, I'd like to create a Jackrabbit 2.13.4 release from trunk.
The list of unresolved issues for 2.13.4 is:
https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%202.13.4%20AND%20project%20%3D%20JCR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
I
[
https://issues.apache.org/jira/browse/JCR-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved JCR-4038.
-
Resolution: Fixed
> NodeLocalNameTest should expect InvalidQueryException for certain incorrect
>
Hi there,
so last year, in the context of OAK-3265, we changed tests in
NodeLocalNameTest (jackrabbit-jcr-tests, which is the TCK...).
Unfortunately, this happened without a related JIRA ticket in the JCR
project, and thus went into releases without even being mentioned in the
change logs.
Konrad Windszus created JCRVLT-131:
--
Summary: Document InstallHooks
Key: JCRVLT-131
URL: https://issues.apache.org/jira/browse/JCRVLT-131
Project: Jackrabbit FileVault
Issue Type:
Julian Reschke created JCR-4038:
---
Summary: NodeLocalNameTest should expect InvalidQueryException for
certain incorrect parameters
Key: JCR-4038
URL: https://issues.apache.org/jira/browse/JCR-4038
Julian Reschke created JCR-4039:
---
Summary: Queries should reject invalid nodeLocalName parameters
Key: JCR-4039
URL: https://issues.apache.org/jira/browse/JCR-4039
Project: Jackrabbit Content Repository
On 2016-10-04 15:36, Julian Reschke wrote:
Hi there,
so last year, in the context of OAK-3265, we changed tests in
NodeLocalNameTest (jackrabbit-jcr-tests, which is the TCK...).
Unfortunately, this happened without a related JIRA ticket in the JCR
project, and thus went into releases without
[
https://issues.apache.org/jira/browse/JCR-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15545400#comment-15545400
]
Julian Reschke commented on JCR-4038:
-
Note that his changes make the current Jackrabbit implementation
[
https://issues.apache.org/jira/browse/JCR-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15545389#comment-15545389
]
Julian Reschke commented on JCR-4038:
-
trunk: [r1710139|http://svn.apache.org/r1710139]
[
https://issues.apache.org/jira/browse/JCR-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke closed JCR-4038.
---
> NodeLocalNameTest should expect InvalidQueryException for certain incorrect
> parameters
>
[
https://issues.apache.org/jira/browse/JCR-4038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-4038:
Fix Version/s: 2.11.2
> NodeLocalNameTest should expect InvalidQueryException for certain incorrect
[
https://issues.apache.org/jira/browse/JCR-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke updated JCR-3913:
Fix Version/s: (was: 2.13.4)
2.11.2
> Test failures: NodeLocalNameTest
>
[
https://issues.apache.org/jira/browse/JCR-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke closed JCR-3913.
---
> Test failures: NodeLocalNameTest
>
>
> Key: JCR-3913
>
[
https://issues.apache.org/jira/browse/JCR-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Reschke resolved JCR-3913.
-
Resolution: Fixed
The issue of tests failing was resolved in October 2015 (2.11.2).
I have created
The Apache Jenkins build system has built Apache Jackrabbit Oak matrix (build
#1188)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Apache%20Jackrabbit%20Oak%20matrix/1188/ to view
the results.
Changes:
[dj] OAK-4860 : Backport OAK-4301 and OAK-4845 - reverted
[ERROR] org.apache.jackrabbit.oak.spi.security.authentication.external.basic:
Version increase required; detected 1.2.0, suggested 1.2.1
Hello Team,
the vote passes as follows:
+1 Davide Giannella
+1 Dominque Jaeggi
+1 Julian Reschke
Thanks for voting. I'll push the release out.
-- Davide
The Apache Jackrabbit community is pleased to announce the release of
Apache Jackrabbit Oak 1.5.11 The release is available for download at:
http://jackrabbit.apache.org/downloads.html
See the full release notes below for details about this release:
Release Notes -- Apache Jackrabbit Oak --
On 3.10.16 4:33 , Robert Munteanu wrote:
* Where are the limitation and how are we going to deal with them?
> Specifically: how do you deal with atomicity when multiple node
> stores
> are mounted? Similarly, how do you guarantee global constraints
> (like
> uniqueness).
We explicitly set
On 2016-10-04 08:43, Chetan Mehrotra wrote:
<>
Hi Team,
Sometime back we discussed the requirement for oak:Resource as a non
referenceable replacement for nt:resource (OAk-4567). This topic was
also discussed on DL [1] and at that time it was decided that changing
the defaults (making
I reverted that commit at r1763270.
2016-10-04 14:09 GMT+02:00 Francesco Mari :
> Yes, I guess I was too fast at enabling that fixture. The version of
> Segment Tar implementing the Checkpoints interface hasn't been
> released and referenced from the rest of Oak yet.
>
>
Yes, I guess I was too fast at enabling that fixture. The version of
Segment Tar implementing the Checkpoints interface hasn't been
released and referenced from the rest of Oak yet.
2016-10-04 14:03 GMT+02:00 Julian Reschke :
> On 2016-10-04 12:08, Julian Reschke wrote:
>>
On 2016-10-04 12:08, Julian Reschke wrote:
[ERROR]
org.apache.jackrabbit.oak.spi.security.authentication.external.basic:
Version increase required; detected 1.2.0, suggested 1.2.1
The above can be mitigated with -Dbase.skip.
With that, I get a test failure at:
Tests in error:
On Tue, Oct 4, 2016 at 12:08 PM, Julian Reschke wrote:
>> [ERROR]
>> org.apache.jackrabbit.oak.spi.security.authentication.external.basic:
>> Version increase required; detected 1.2.0, suggested 1.2.1
this will be resolved soon by committing OAK-4825
On 03/10/2016 12:43, Dominique Jaeggi wrote:
> hi team
>
> On Mon, Oct 3, 2016 at 11:46 AM, Dominique Jaeggi wrote:
>> The SHA1 checksum of the archive is
>> 49173337932d6763b112826d409425929dbd226e.
>>
>> A staged Maven repository is available for review at:
>>
>>
> At least in our DocumentStoreImplementations (Mongo and RDB), making the
> UUID something indexed by the storage (so either Mongo or the relational
> database) should be relatively cheap (after all, the UUID never changes once
> assigned, right?). That would eliminate the indexing overhead in
On 2016-10-04 15:58, Thomas Mueller wrote:
Hi,
I still do not understand, why we do not delegate the UUID
generation/lookup to the persistence instead of insisting it to be just
like any other property index...
The UUID _generation_ is not a problem. (I it a bit slow, but scales well
- no
<>
Hi Team,
Sometime back we discussed the requirement for oak:Resource as a non
referenceable replacement for nt:resource (OAk-4567). This topic was
also discussed on DL [1] and at that time it was decided that changing
the defaults (making nt:resource non referenceable ) is not possible
and
29 matches
Mail list logo