Hudson build is back to stable: Ja ckrabbit-1.5 » Jackrabbit Core #14

See http://hudson.zones.apache.org/hudson/job/Jackrabbit-1.5/org.apache.jackrabbit$jackrabbit-core/14/changes

Re: Hudson build is back to stable: Jackrabbit-1.5 » Jackrabbit Core #14

Hi, Some query tests were temporarily failing in the 1.5 branch. The build got back to stable simply by re-running it, so it looks like a random failure, perhaps due to some synchronization issue. I'm going to push forward with the 1.5 release. If this problem reappears we can treat it as a

[jira] Created: (JCR-1892) Unique ID for org.apache.jackrabbit.value.BinaryValue

Unique ID for org.apache.jackrabbit.value.BinaryValue - Key: JCR-1892 URL: https://issues.apache.org/jira/browse/JCR-1892 Project: Jackrabbit Issue Type: New Feature Components:

Re: [VOTE] Open the sandbox to all Apache committers

+1 cheers stefan On 02.12.2008, at 11:24, Jukka Zitting [EMAIL PROTECTED] wrote: Hi, Opening up the Jackrabbit sandbox area for all Apache committers is something I've been thinking about for some while, and now with the CMIS implementation effort I think we have a good case where doing

Re: [VOTE] Open the sandbox to all Apache committers

[X] +1 Open the sandbox to all Apache committers regards marcel

[jira] Commented: (JCR-1890) spi2dav: create RepositoryFactory implementation

[ https://issues.apache.org/jira/browse/JCR-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652362#action_12652362 ] angela commented on JCR-1890: - should we qualify those two with jcr2spi in their name somewhere?

[VOTE] Release Apache Jackrabbit 1.5.0

Hi, I have posted a candidate for the Apache Jackrabbit 1.5.0 release at http://people.apache.org/~jukka/jackrabbit/1.5.0/ See the RELEASE-NOTES.txt file (also included at the end of this message) for details on release contents and latest changes. The release candidate is a jar archive of

Re: jcr-cmis sandbox

On 2 Dec 2008, at 20:04, Dominique Pfister wrote: -- + rest + ws Just as an observation, I think it's insane having two different protocols for this standard. It sounds like two factions in the standards group that could never agree. -- Torgeir Veimo [EMAIL PROTECTED]

[jira] Created: (JCR-1890) spi2dav: create RepositoryFactory implementation

spi2dav: create RepositoryFactory implementation Key: JCR-1890 URL: https://issues.apache.org/jira/browse/JCR-1890 Project: Jackrabbit Issue Type: New Feature Components: sandbox

Re: [VOTE] Open the sandbox to all Apache committers

[X] +1 Open the sandbox to all Apache committers As an informal rule I'd still expect external committers who choose to commit to our sandbox to be subscribed on dev@ and to follow at least the relevant parts of [EMAIL PROTECTED] Yes, that rule should be clearly given, it's good to see what

[jira] Resolved: (JCR-1836) Persistence: support property databaseType

[ https://issues.apache.org/jira/browse/JCR-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Mueller resolved JCR-1836. - Resolution: Fixed Committed in revision 722463 (trunk) Persistence: support property

[jira] Created: (JCR-1891) jcr2spi: use Soft refs for hierarchy

jcr2spi: use Soft refs for hierarchy Key: JCR-1891 URL: https://issues.apache.org/jira/browse/JCR-1891 Project: Jackrabbit Issue Type: Improvement Components: jackrabbit-jcr2spi

[jira] Resolved: (JCR-1886) jcr2spi: Unprocessed ItemInfos call to RepositoryService#getItemInfos

[ https://issues.apache.org/jira/browse/JCR-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela resolved JCR-1886. - Resolution: Fixed jcr2spi: Unprocessed ItemInfos call to RepositoryService#getItemInfos

[jira] Resolved: (JCR-1891) jcr2spi: use Soft refs for hierarchy

[ https://issues.apache.org/jira/browse/JCR-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela resolved JCR-1891. - Resolution: Fixed jcr2spi: use Soft refs for hierarchy

Re: Files for binary properties

Hi, Just recently there was a discussion about getting the unique identifier for a binary value. I created an issue: https://issues.apache.org/jira/browse/JCR-1892 I am currently using the XMLPersistenceManager. You should consider using a bundle database persistence manager. See also

Re: Files for binary properties

Hi, On Tue, Dec 2, 2008 at 2:19 PM, Charles Brooking [EMAIL PROTECTED] wrote: When using a datastore I assumed files might not be directly stored on the (operating system) filesystem. Currently, I need a direct mapping to files so I can pass file paths to other programs for processing.

Re: Files for binary properties

Thomas Müller wrote: Just recently there was a discussion about getting the unique identifier for a binary value. I created an issue: https://issues.apache.org/jira/browse/JCR-1892 I am currently using the XMLPersistenceManager. You should consider using a bundle database persistence

[jira] Commented: (JCR-1890) spi2dav: create RepositoryFactory implementation

[ https://issues.apache.org/jira/browse/JCR-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12652360#action_12652360 ] Marcel Reutegger commented on JCR-1890: ---

[jira] Resolved: (JCR-1890) spi2dav: create RepositoryFactory implementation

[ https://issues.apache.org/jira/browse/JCR-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela resolved JCR-1890. - Resolution: Fixed added initial draft of a RepositoryFactory implementation based on the factory interface

jcr-cmis sandbox

Hi, After having had a first look at the CMIS specification, I decided to start off with the jcr-cmis implementation. I therefore created a jcr-cmis sandbox with the following initial structure: jcr-cmis -- + server + rest + ws I intend to start working on the server/rest subtree

Re: jcr-cmis sandbox

Dominique Pfister wrote: Hi, After having had a first look at the CMIS specification, I decided to start off with the jcr-cmis implementation. I therefore created a jcr-cmis sandbox with the following initial structure: jcr-cmis -- + server + rest + ws I intend to start working on

[VOTE] Open the sandbox to all Apache committers

Hi, Opening up the Jackrabbit sandbox area for all Apache committers is something I've been thinking about for some while, and now with the CMIS implementation effort I think we have a good case where doing so would clearly be helpful. Thus I propose that we grant all Apache committers write

Re: [VOTE] Open the sandbox to all Apache committers

+1 Cheers Dominique On Tue, Dec 2, 2008 at 11:24 AM, Jukka Zitting [EMAIL PROTECTED] wrote: Hi, Opening up the Jackrabbit sandbox area for all Apache committers is something I've been thinking about for some while, and now with the CMIS implementation effort I think we have a good case

Apache JCR Commons

Hi, Based on earlier discussion [1] I would like to propose that we start a new Apache JCR Commons subproject within Jackrabbit. See below what this could mean in practice. As usual, comments are welcome! COMPONENTS The JCR Commons subproject would take over the development and maintenance of

Re: Apache JCR Commons

On Tue, Dec 2, 2008 at 4:52 PM, Jukka Zitting [EMAIL PROTECTED] wrote: COMPONENTS The JCR Commons subproject would take over the development and maintenance of the following components: * jackrabbit-jcr-commons * jackrabbit-jcr-tests * jackrabbit-jcr-benchmark *

Re: Apache JCR Commons

Hi, On Tue, Dec 2, 2008 at 5:42 PM, Alexander Klimetschek [EMAIL PROTECTED] wrote: Do all these projects solely rely on the JCR API? Some of them have dependencies to other commons projects and/or to external components. For example jcr-rmi depends on jcr-commons and slf4j. They shouldn't be

Re: jcr-cmis sandbox

Also, I don't think we should implement any of the HTTP extensions in the AtomPub binding -- they are neither necessary nor desirable. We should show the TC how to implement it right, not just implement whatever they suggest. very good point! this also puts us into a good position to file