Hudson build is unstable: Jackrabbit-trunk #1419

See

Hudson build is unstable: Jackrab bit-trunk » Jackrabbit Core #1419

See

Hudson build is back to normal : Jackra bbit-trunk » Jackrabbit Parent POM #1419

See

[VOTE] Release Apache Jackrabbit 2.2.1

Hi, A candidate for the Jackrabbit 2.2.1 release is available at: http://people.apache.org/~jukka/jackrabbit/2.2.1/ The release candidate is a zip archive of the sources in: http://svn.apache.org/repos/asf/jackrabbit/tags/2.2.1/ The SHA1 checksum of the archive is dfe0a621f91ae765a36b3

[jira] Commented: (JCR-2857) Support sequential (non-random) node ids

[ https://issues.apache.org/jira/browse/JCR-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977893#action_12977893 ] Jukka Zitting commented on JCR-2857: The UUIDs of referenceable nodes must be globally un

[jira] Updated: (JCR-2855) Writers blocked forever when waiting on update operations

[ https://issues.apache.org/jira/browse/JCR-2855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-2855: --- Component/s: jackrabbit-core You tested this with 2.1.3, right? This seems related to JCR-2820, but is

Re: Build failed in Hudson: Jackrabbit-trunk » Jack rabbit Parent POM #1418

Hi, On Wed, Jan 5, 2011 at 6:37 PM, Apache Hudson Server wrote: > [INFO] Error deploying artifact: Failed to transfer file: > https://repository.apache.org/content/repositories/snapshots/org/apache/jackrabbit/jackrabbit-parent/2.3-SNAPSHOT/jackrabbit-parent-2.3-20110105.170846-49.pom. > Return

Build failed in Hudson: Jackrabbit-trunk #1418

See Changes: [jukka] JCR-2843: ConstraintSplitter.getSelectorNames doesn't support FullTextSearch constraints Patch by Edouard Hue -- Started by an SCM change Building remotely on solar

Build failed in Hudson: Jackrabbit- trunk » Jackrabbit Parent POM #1418

See -- channel started <===[HUDSON REMOTING CAPACITY]===> Executing Maven: -B -f /export/home/hudson/hudson-slave/workspace/Jackrabbit-trunk/trunk/pom.

[jira] Commented: (JCR-2859) Make open scoped locks recoverable

[ https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977861#action_12977861 ] Carsten Ziegeler commented on JCR-2859: --- I'm fine with Jukka's proposal as well - my id

[jira] Resolved: (JCR-2856) Upgrade to latest SLF4J and Logback

[ https://issues.apache.org/jira/browse/JCR-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCR-2856. Resolution: Fixed Upgraded to SLF4J 1.6.1 and Logback 0.9.27 in revision 1055075. > Upgrade to lates

[jira] Commented: (JCR-2415) Update Lucene to 3.0

[ https://issues.apache.org/jira/browse/JCR-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977848#action_12977848 ] Jukka Zitting commented on JCR-2415: Anyone interested in working on this? I'd love to he

[jira] Resolved: (JCR-2849) Make QueryResult.getNodes() work also for certain join queries

[ https://issues.apache.org/jira/browse/JCR-2849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCR-2849. Resolution: Won't Fix Assignee: Jukka Zitting Resolving as Won't Fix, since it's possible (and

[jira] Resolved: (JCR-2791) Potential deadlock in LockManagerImpl

[ https://issues.apache.org/jira/browse/JCR-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCR-2791. Resolution: Duplicate Resolving as a duplicate of JCR-2699. I did a quick review of the relevant code

[jira] Commented: (JCR-2859) Make open scoped locks recoverable

[ https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977838#action_12977838 ] Cédric Damioli commented on JCR-2859: - I tend to agree with Stefan that it's the client r

[jira] Commented: (JCR-2859) Make open scoped locks recoverable

[ https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977821#action_12977821 ] Jukka Zitting commented on JCR-2859: I would treat this as an administration operation th

[jira] Commented: (JCR-2622) Index analizers that extends StandardAnalyzer need to implement reusableTokenStream() since jackrabbit 2.1

[ https://issues.apache.org/jira/browse/JCR-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977814#action_12977814 ] Jukka Zitting commented on JCR-2622: OK, thanks for the detailed review of the issue! >

RE: Jackrabbit 2.2.1 release plan

Hi, From: Edouard Hue [mailto:edouard@gmail.com] > This one is an easily fixed regression from 2.1 : > https://issues.apache.org/jira/browse/JCR-2843 Thanks! The fix is now in 2.2.1. BR, Jukka Zitting

[jira] Updated: (JCR-2843) ConstraintSplitter.getSelectorNames doesn't support FullTextSearch constraints

[ https://issues.apache.org/jira/browse/JCR-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-2843: --- Resolution: Fixed Fix Version/s: 2.2.1 Assignee: Jukka Zitting Status: Resolv

[jira] Commented: (JCR-2859) Make open scoped locks recoverable

[ https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977805#action_12977805 ] Carsten Ziegeler commented on JCR-2859: --- > LockManager.lock(...) returns a Lock instanc

[jira] Commented: (JCR-2859) Make open scoped locks recoverable

[ https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977804#action_12977804 ] Carsten Ziegeler commented on JCR-2859: --- Session scoped locks do not work in a clustere

[jira] Commented: (JCR-2859) Make open scoped locks recoverable

[ https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977797#action_12977797 ] Stefan Guggisberg commented on JCR-2859: > There is a theoretical way of adding the l

[jira] Commented: (JCR-2859) Make open scoped locks recoverable

[ https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977716#action_12977716 ] Carsten Ziegeler commented on JCR-2859: --- There is no API in JCR to get the lock token a

[jira] Commented: (JCR-2859) Make open scoped locks recoverable

[ https://issues.apache.org/jira/browse/JCR-2859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977706#action_12977706 ] Cédric Damioli commented on JCR-2859: - It could also be possible to store the lock tocken

[jira] Created: (JCR-2859) Make open scoped locks recoverable

Make open scoped locks recoverable -- Key: JCR-2859 URL: https://issues.apache.org/jira/browse/JCR-2859 Project: Jackrabbit Content Repository Issue Type: New Feature Components: locks Affects Ve

[jira] Commented: (JCR-2857) Support sequential (non-random) node ids

[ https://issues.apache.org/jira/browse/JCR-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977678#action_12977678 ] Thomas Mueller commented on JCR-2857: - Sequential node ids are much faster than random no