[
https://issues.apache.org/jira/browse/JCR-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-3895:
Issue Type: New Feature (was: Bug)
> Add handler to handle webdav LOCK requests
> ---
[
https://issues.apache.org/jira/browse/JCR-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-3895:
Component/s: jackrabbit-jcr-server
> Add handler to handle webdav LOCK requests
>
On 03/08/2015 14:34, Davide Giannella wrote:
> Hello team,
>
> in order to unlock the release of Oak 1.3.4 we should release JR 2.10.2.
>
> I'm planning to do it tomorrow (4/8) around 11AM CEST.
>
The release is currently blocked as it fails constantly on
Failed tests:
IndexingQueueTest>Abstract
[
https://issues.apache.org/jira/browse/JCR-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653409#comment-14653409
]
Satya Deep Maheshwari commented on JCR-3895:
[~tripod], if you haven't started o
Hi,
With the help of git bisect I identified the following commit as the
culprit [0].
4bc1dba12fd8ce8ec2b95e5da2e44387db21ba3e is the first bad commit
commit 4bc1dba12fd8ce8ec2b95e5da2e44387db21ba3e
Author: Unico Hommes
Date: Wed Jun 24 10:21:04 2015 +
verify double
Hi,
Following my earlier message, it looks like JCR-3888 [0] is not marked as
resolved yet, but I have no insight into what the status is.
I would suggest reverting the commit (a fix should not introduce failing
tests anyways) and cutting the release without it.
best,
alex
[0] https://issues.ap
[
https://issues.apache.org/jira/browse/JCR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653434#comment-14653434
]
Alex Parvulescu commented on JCR-3888:
--
this commit looks like it introduced a regressi
[
https://issues.apache.org/jira/browse/JCR-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-3880.
-
Resolution: Fixed
Fix Version/s: 2.10.2
Committed revision 1694048.
> Allow to add/remove group members by
[
https://issues.apache.org/jira/browse/JCR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653624#comment-14653624
]
Davide Giannella commented on JCR-3888:
---
in http://svn.apache.org/r1694059 I revert th
Davide Giannella created JCR-3896:
-
Summary: Release Jackrabbit 2.10.2
Key: JCR-3896
URL: https://issues.apache.org/jira/browse/JCR-3896
Project: Jackrabbit Content Repository
Issue Type: Tas
[
https://issues.apache.org/jira/browse/JCR-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated JCR-3860:
--
Fix Version/s: (was: 2.10.2)
2.10.3
> Properly expose missing values in Tim
[
https://issues.apache.org/jira/browse/JCR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated JCR-3888:
--
Fix Version/s: (was: 2.10.2)
2.10.3
> Possible dead lock in SharedItemState
[
https://issues.apache.org/jira/browse/JCR-3863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davide Giannella updated JCR-3863:
--
Fix Version/s: (was: 2.10.2)
2.10.3
> org.apache.jackrabbit.api.observation
This issue was fixed, see for reference also [1]. I just forgot to
resolve it. I will look into the failing test. Looks somewhat
unrelated at first glance.
1. https://issues.onehippo.com/browse/REPO-1216
On Tue, Aug 4, 2015 at 12:38 PM, Alex Parvulescu
wrote:
> Hi,
>
> Following my earlier messa
[
https://issues.apache.org/jira/browse/JCR-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653652#comment-14653652
]
Unico Hommes commented on JCR-3888:
---
This deadlock is quite serious. Might want to hold of
On Mon, Aug 3, 2015 at 8:14 AM, Clay Ferguson wrote:
> I looked at that readme page (oak-pojosr). I like the idea of simplifying
> use of osgi, or embedding it. It reminds me a bit of how SpringBoot actually
> embeds an instance of Tomcat, so deployment is simple and easy for web apps.
>
> Having
Robert,
Not to turn this email list into a theoretical discussion, but I'll say one
thing, and then we can carry on the conversation privately or in different
forum...
I think *the* primary reason OSGi has a place in the world, is because it
can make completely incompatible set of things be able t
Hi,
I don't think Robert (or anyone else) is saying that there *shouldn't* be a
Spring Boot-based distribution which uses Oak. But the Jackrabbit project
wouldn't necessarily be the right place for this.
Regards,
Justin
On Tue, Aug 4, 2015 at 10:08 AM Clay Ferguson wrote:
> Robert,
> Not to tur
[
https://issues.apache.org/jira/browse/JCR-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653874#comment-14653874
]
Tobias Bocanegra commented on JCR-3895:
---
I haven't started yet - otherwise I would hav
​Justin,
Correct. I was laying out the details of how JCR should relate to
SpringBoot. I think I got it right. SpringBoot would include a JCR project,
not the other way around. Jackrabbit would never depend on SpringBoot.
However, if I were the architect of Oak, it would be using Spring Core
(etc)
A candidate for the Jackrabbit 2.10.2 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/2.10.2/
The release candidate is a zip archive of the sources in:
https://svn.apache.org/repos/asf/jackrabbit/tags/2.10.2/
The SHA1 checksum of the archive is
a4fc082b0f0ba7
[X] -1 Do not release this package because...
it says
svn: E17: URL
'https://svn.apache.org/repos/asf/jackrabbit/tags/2.10.2' doesn't exist
and indeed it doesn't. By looking at SVN I can find that since 2.10.1
the tag created are `jackrabbit-VERSION` rather than `VERSION`.
I searched throug
22 matches
Mail list logo
