Re: Java 5 in Jackrabbit 2.0?

Jukka Zitting wrote: > I would propose that we go with option 2, i.e. make Jackrabbit 2.0 > require Java 5. +1 I don't see a reason why we have to wait for the specification to require Java 5. the API wouldn't benefit from that move anyway, unless it gets heavily restructured. regards marcel

Re: Maven 2.0.9+ for Jackrabbit (Was: Build failed in Hudson: Jackrabbit-trunk-java14 #70)

Hi, On Sat, Feb 7, 2009 at 1:54 PM, Jukka Zitting wrote: > Personally I wouldn't mind making Maven 2.0.9 a requirement. Looks like there's a consensus on this, so I'll update the POM to explicitly require Maven 2.0.9. BR, Jukka Zitting

Re: Java 5 in Jackrabbit 2.0?

> I would propose that we go with option 2, i.e. make Jackrabbit 2.0 > require Java 5. +1 make Jackrabbit 2.0 require Java 5. The default jar files could be compiled with "-target 1.5", but we could test and document how to use Retroweaver ( http://retroweaver.sourceforge.net/ ) to convert it to

[jira] Created: (JCR-1972) Preserving UUID and document version history on repository migration

Preserving UUID and document version history on repository migration Key: JCR-1972 URL: https://issues.apache.org/jira/browse/JCR-1972 Project: Jackrabbit Content Repository

[jira] Updated: (JCR-1972) Preserving UUID and document version history on repository migration

[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1972: Attachment: Jackrabbit_modifications.pdf This PDF shows the modifications needed in the jackrabbit core to pr

[jira] Resolved: (JCRSITE-10) Parent pom requires Maven 2.0.9 or higher

[ https://issues.apache.org/jira/browse/JCRSITE-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCRSITE-10. -- Resolution: Fixed Fix Version/s: parent 3 Assignee: Jukka Zitting The consensus

[jira] Commented: (JCR-1972) Preserving UUID and document version history on repository migration

[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671808#action_12671808 ] Alexander Klimetschek commented on JCR-1972: Could you provide the diff in a norm

Re: Java 5 in Jackrabbit 2.0?

Jukka Zitting wrote: > I would propose that we go with option 2, i.e. make Jackrabbit 2.0 > require Java 5. +1 Regards, Alex -- Alexander Klimetschek alexander.klimetsc...@day.com

[jira] Created: (JCRSITE-11) Prevent accidental release deployments

Prevent accidental release deployments -- Key: JCRSITE-11 URL: https://issues.apache.org/jira/browse/JCRSITE-11 Project: Jackrabbit Site Issue Type: Improvement Components: parent Rep

Build failed in Hudson: Jackrabbit-trunk-java14 #71

See http://hudson.zones.apache.org/hudson/job/Jackrabbit-trunk-java14/71/changes Changes: [jukka] JCR-1971: Use the new Jackrabbit parent POM The new POM requires 2.0.9. Declare it explicitly as the minimum version here until JCRSITE-10 is fixed and released in parent:3. --

[jira] Commented: (JCR-1953) Jackrabbit on JBoss: ItemStateCache seems to be invalid

[ https://issues.apache.org/jira/browse/JCR-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671835#action_12671835 ] Marcel Reutegger commented on JCR-1953: --- Moritz, can you please check if this is still

Re: Build failed in Hudson: Jackrabbit-trunk-java14 #71

Hi, On Mon, Feb 9, 2009 at 1:46 PM, Apache Hudson Server wrote: > [INFO] Trace > java.lang.OutOfMemoryError Oh, that's a new one. I updated the Hudson build configuration to use Maven 2.0.9 instead of 2.0.8, and it seems like there's a difference in memory usage across these versions. BR, Jukk

[jira] Updated: (JCR-1972) Preserving UUID and document version history on repository migration

[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paco Avila updated JCR-1972: Attachment: JCR-1972.patch Patch solicited by Alexander Klimetschek. This patch works with jackrabbit-core-1

[jira] Issue Comment Edited: (JCR-1972) Preserving UUID and document version history on repository migration

[ https://issues.apache.org/jira/browse/JCR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671842#action_12671842 ] monkiki edited comment on JCR-1972 at 2/9/09 5:10 AM: - Patch solicite

[jira] Resolved: (JCR-1971) Use the new Jackrabbit parent POM

[ https://issues.apache.org/jira/browse/JCR-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCR-1971. Resolution: Fixed I've updated the main Jackrabbit project as well as commons/jcr-rmi and sandbox/jc

[jira] Commented: (JCR-1967) Impossible comparison in NodeTypeImpl

[ https://issues.apache.org/jira/browse/JCR-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671874#action_12671874 ] Stefan Guggisberg commented on JCR-1967: FWIW: i guess the code in question is base

Understanding Jackrabbit's lucene syntax

This is probably a rather obvious question, but I'm trying to understand the queries that Jackrabbit is putting together and figured I'd fire off an email to see if anyone could help me out quick. My xpath query is "//child[foo/@foo = 'bar']" and the lucene query is: +(+(_:PROPERTIES:1:foo[bar _:PR

Jackrabbit Lucene Query Syntax

This is probably a rather obvious question, but I'm trying to understand the queries that Jackrabbit is putting together and figured I'd fire off an email to see if anyone could help me out quick. My xpath query is "//child[foo/@foo = 'bar']" and the lucene query is: +(+(_:PROPERTIES:1:foo[bar _:PR

Re: Jackrabbit Lucene Query Syntax

Hi, On Mon, Feb 9, 2009 at 8:17 PM, Dan Diephouse wrote: > This is probably a rather obvious question, but I'm trying to understand the > queries that Jackrabbit is putting together and figured I'd fire off an > email to see if anyone could help me out quick. My xpath query is > "//child[foo/@foo

Moving to DFS System ..

Dear All, I have used jackrabbit 1.4 and was successful running in my local environment with the repository provided by JR itself. Now that we have our own DFS system I would like to change the existing configuration to our DFS instead using JR repository ... May I know how do I do this ..