On 2012-02-03 19:44, Michael Dürig wrote:
...
Sounds very interesting.
I have a comment that may not even apply to this work, but still:
recently a JCR issue was opened because Jackrabbit doesn't fire
compliant NODE_MOVE events for reorder operations. Turns out that
Jackrabbit doesn't keep
Hi,
While working on a new transient space implementation [1] I discovered
that recreating a list of changes from transient modifications to the
hierarchy is like opening a can of worms. Rethinking things it turned
out, that it is much simpler to directly consolidate the change log.
This app
Hi Jukka,
> but for now I'd just leave things as-is.
I agree with considering this an accident, no need to change all the rules
for that.
thanks,
alex
On Fri, Feb 3, 2012 at 4:39 PM, Jukka Zitting wrote:
> Hi,
>
> On Fri, Feb 3, 2012 at 4:21 PM, Alex Parvulescu
> wrote:
> > How can I reopen
Hi,
On Fri, Feb 3, 2012 at 4:21 PM, Alex Parvulescu
wrote:
> How can I reopen a closed issue?
We're using the no-reopen-closed workflow, which explicitly prevents
reopening of closed issues. The idea behind this is to freeze the list
of issues resolved in a given release after that release has b
Signatures are ok, all tests pass:
+1 !
Bart
On Fri, Feb 3, 2012 at 1:53 PM, Jukka Zitting wrote:
> Hi,
>
> A candidate for the Jackrabbit 2.4.0 release is available at:
>
> http://people.apache.org/~jukka/jackrabbit/2.4.0/
>
> The release candidate is a zip archive of the sources in:
>
>
Hi guys,
How can I reopen a closed issue?
I have resolved an issue [0] but shortly after it was accidentally marked
as 'Closed'. This is not standard workflow, so I'd like to turn it into
'Resolved' again until the actual release happens.
How do I do that?
thanks,
alex
[0] https://issues.apach
[
https://issues.apache.org/jira/browse/JCR-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199761#comment-13199761
]
Alex Parvulescu commented on JCR-3050:
--
hi, you are welcome :)
by the way, you're not
Hi,
On Fri, Feb 3, 2012 at 3:06 PM, Torgeir Veimo wrote:
> On 3 February 2012 22:53, Jukka Zitting wrote:
>> A candidate for the Jackrabbit 2.4.0 release is available at:
>
> Feb 4, 2012 12:04:30 AM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web applicati
+1
checks pass
alex
On Fri, Feb 3, 2012 at 1:53 PM, Jukka Zitting wrote:
> Hi,
>
> A candidate for the Jackrabbit 2.4.0 release is available at:
>
>http://people.apache.org/~jukka/jackrabbit/2.4.0/
>
> The release candidate is a zip archive of the sources in:
>
>http://svn.apache.org/rep
[
https://issues.apache.org/jira/browse/JCR-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Buchmann closed JCR-3050.
---
oh, ok. guess with the right exception i will understand what i do wrong :-)
actually the root node is rep
[
https://issues.apache.org/jira/browse/JCR-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu resolved JCR-3050.
--
Resolution: Fixed
Fix Version/s: 2.5
The NPE happens because you re trying to delete the r
On 3 February 2012 22:53, Jukka Zitting wrote:
> A candidate for the Jackrabbit 2.4.0 release is available at:
Feb 4, 2012 12:04:30 AM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
SEVERE: The web application [/main] appears to have started a thread
named [Timer-13] but has
[
https://issues.apache.org/jira/browse/JCR-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu updated JCR-3219:
-
Attachment: JCR-3219-test.patch
I'm having some trouble reproducing this issue.
I'm using trunk as
using check-release.sh:
+1
On 3.2.12 12:53, Jukka Zitting wrote:
Hi,
A candidate for the Jackrabbit 2.4.0 release is available at:
http://people.apache.org/~jukka/jackrabbit/2.4.0/
The release candidate is a zip archive of the sources in:
http://svn.apache.org/repos/asf/jackrabbi
Hi,
A candidate for the Jackrabbit 2.4.0 release is available at:
http://people.apache.org/~jukka/jackrabbit/2.4.0/
The release candidate is a zip archive of the sources in:
http://svn.apache.org/repos/asf/jackrabbit/tags/2.4.0/
The SHA1 checksum of the archive is ff9332ffb571ebd3b2271
[
https://issues.apache.org/jira/browse/JCR-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-3203.
Resolution: Fixed
Resolving for 2.4 to get the change that was already made reflected in the
release
[
https://issues.apache.org/jira/browse/JCR-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199632#comment-13199632
]
Jukka Zitting commented on JCR-3225:
Merged to the 2.4 branch in revision 1240068.
[
https://issues.apache.org/jira/browse/JCR-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Parvulescu resolved JCR-3225.
--
Resolution: Fixed
Fix Version/s: 2.4
I wasn't able to see the ConcurrentModificationExcept
18 matches
Mail list logo