[
https://issues.apache.org/jira/browse/JCR-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Köll updated JCR-3999:
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed in revision 1755017.
>
Hi All,
I am trying to write a test case for pull request [0].
For writing a test case for this, I will be needing to create a node but there
is no repository resource available in this bundle.
So can you please let me do I need to add repository resource in this bundle
or is there any other
[
https://issues.apache.org/jira/browse/JCR-3975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Woonsan Ko updated JCR-3975:
Flags: Patch
> Commons-VFS Datastore implementation
>
>
>
Hi Kiran,
Please find answers inline below.
From: "Suthrave, Kiran"
> We have been using JCR 1.4 version.
You're probably referring to Oak 1.4, right?
> Recently we encountered lease check failure error.
> I have few queries regarding this:
> ·Could you please help understand how
[
https://issues.apache.org/jira/browse/JCR-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Tagliani updated JCR-4001:
---
Attachment: JCR-4001.patch
Attaching patch
> When using Node.getProperties(String namePattern) also
[
https://issues.apache.org/jira/browse/JCR-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Tagliani updated JCR-4001:
---
Status: Patch Available (was: Open)
> When using Node.getProperties(String namePattern) also child
Luca Tagliani created JCR-4001:
--
Summary: When using Node.getProperties(String namePattern) also
child nodes are processed
Key: JCR-4001
URL: https://issues.apache.org/jira/browse/JCR-4001
Project:
[
https://issues.apache.org/jira/browse/JCRVLT-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329008#comment-15329008
]
angela edited comment on JCRVLT-111 at 8/2/16 2:25 PM:
---
initial untested draft
[
https://issues.apache.org/jira/browse/JCRVLT-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCRVLT-111:
--
Assignee: Tobias Bocanegra
Status: Patch Available (was: Open)
[~tripod], may i ask you to take a look
-- Forwarded message --
From: Alexej Sailer
Date: 2016-08-02 10:13 GMT+02:00
Subject: Speed up initial Bundle load > 10k from database
To: us...@jackrabbit.apache.org
I'm using jackrabbit and from time to time it happens, that I have more
than 10k
Hi,
The vote passes as follows:
+1 Francesco Mari
+1 Michael Dürig
+1 Alex Parvulescu
Thanks for voting. I'll push the release out.
Michael
On 29.7.16 12:01 , Michael Dürig wrote:
Hi,
We solved 8 issues in this release:
https://issues.apache.org/jira/browse/OAK/fixforversion/12338000/
+1, I like this approach. It will result in some additional emails. But
I consider this a good thing as it gives those issues we want to address
the required visibility. Furthermore most of the noise can actually be
avoided by setting realistic fix versions in the first place and
checking
Hi,
On Mon, Aug 1, 2016 at 6:35 PM, Davide Giannella wrote:
>
> Please vote on releasing this package as Apache Jackrabbit Oak 1.5.7.
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 Jackrabbit PMC votes are cast.
+1 Release this
[X] +1 Release this package as Apache Jackrabbit Oak 1.5.7
Hi ,
We have been using JCR 1.4 version.
Recently we encountered lease check failure error.
I have few queries regarding this:
* Could you please help understand how lease check works ?
* What are the scenarios lease check will fail?
* How to custom handle
The main topic seems to be that we need a way to identify the issues
that we want to solve for a stable release of oak-segment-tar. In a
quick offline conversation with Michael, we came up with the following
ideas - to be discussed - to track issues.
1. If an issue is not essential for the stable
16 matches
Mail list logo