[jira] [Created] (JCR-3594) how to create a new repository programmatically or how to create a new workspace in jack rabbit?

murali created JCR-3594: --- Summary: how to create a new repository programmatically or how to create a new workspace in jack rabbit? Key: JCR-3594 URL: https://issues.apache.org/jira/browse/JCR-3594 Project:

[jira] [Commented] (JCR-3594) how to create a new repository programmatically or how to create a new workspace in jack rabbit?

[ https://issues.apache.org/jira/browse/JCR-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13656908#comment-13656908 ] David Buchmann commented on JCR-3594: - each jackrabbit has exactly one repository. to

[jira] [Resolved] (JCR-3594) how to create a new repository programmatically or how to create a new workspace in jack rabbit?

[ https://issues.apache.org/jira/browse/JCR-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-3594. --- Resolution: Invalid Fix Version/s: (was: 2.4.3) Please use the mailing list for

[jira] [Commented] (JCR-3594) how to create a new repository programmatically or how to create a new workspace in jack rabbit?

[ https://issues.apache.org/jira/browse/JCR-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657042#comment-13657042 ] murali commented on JCR-3594: - can u please have any specific code to this ..some POC

[jira] [Commented] (JCR-3568) Property.getBinary().getStream() files in tempDir not removed by InputStream.close() nor by Binary.dispose()

[ https://issues.apache.org/jira/browse/JCR-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657732#comment-13657732 ] Tobias Bocanegra commented on JCR-3568: --- I can't reproduce the OOME, but I get failing

[jira] [Updated] (JCR-3568) Property.getBinary().getStream() files in tempDir not removed by InputStream.close() nor by Binary.dispose()

[ https://issues.apache.org/jira/browse/JCR-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tobias Bocanegra updated JCR-3568: -- Attachment: jcr3568-r1482639.patch new patch that implements a ref counter to avoid disposal of

[jira] [Commented] (JCR-3568) Property.getBinary().getStream() files in tempDir not removed by InputStream.close() nor by Binary.dispose()

[ https://issues.apache.org/jira/browse/JCR-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13657781#comment-13657781 ] Tobias Bocanegra commented on JCR-3568: --- unfortunately the patch fixes some problems

[RESULT] [VOTE] Release Apache Jackrabbit Oak 0.7

Hi, On Mon, May 6, 2013 at 7:57 PM, Jukka Zitting ju...@apache.org wrote: Please vote on releasing this package as Apache Jackrabbit Oak 0.7. The vote passes as follows: +1 Alex Parvulescu +1 Claus Köll +1 Jukka Zitting +1 Julian Reschke Thanks! I'll push the release out. BR,

UserImportTest.testImportGroupIntoUsersTree failing

hi, I see a test failing recently: UserImportTest.testImportGroupIntoUsersTree I'm not really sure why/when this started happening, I'll create an issue and mark it as ignored. The travis CI build don't show it but it also missed the lucene tests that are failing so we might want to take

Re: travis notifications

Hi, On Tue, May 14, 2013 at 4:36 PM, Marcel Reutegger mreut...@adobe.com wrote: the last travis notification I got via the oak-dev list was from yesterday for a successful build [0]. travis is broken or this is due to how we configure the travis build. all builds after 1521 failed [1] and I

Re: travis notifications

hi, I fully agree with Marcel. As previously stated (on Jukka's reference discussion) I think we need to see the failures each time, otherwise we don't react accordingly. The proper way to handle a failure is to create a jira issue and mark the test as ignored, this practice also keeps the noise

Re: travis notifications

Hi, On Tue, May 14, 2013 at 4:55 PM, Alex Parvulescu alex.parvule...@gmail.com wrote: As previously stated (on Jukka's reference discussion) I think we need to see the failures each time, otherwise we don't react accordingly. Do we have evidence of cases where we haven't reacted accordingly

Re: [Still Failing] apache/jackrabbit-oak#1531 (trunk - d660a99)

I've created OAK-821 for this failed test, next I'll try mark the lucene failures as known issues On Tue, May 14, 2013 at 4:08 PM, Travis CI notificati...@travis-ci.orgwrote: Build Update for apache/jackrabbit-oak - Build: #1531 Status: Still Failing

[Still Failing] apache/jackrabbit-oak#1532 (trunk - f56c447)

Build Update for apache/jackrabbit-oak - Build: #1532 Status: Still Failing Duration: 34 minutes and 54 seconds Commit: f56c447 (trunk) Author: Alexandru Parvulescu Message: OAK-821 UserImportTest.testImportGroupIntoUsersTree failing git-svn-id:

[Still Failing] apache/jackrabbit-oak#1534 (trunk - 55073d6)

Build Update for apache/jackrabbit-oak - Build: #1534 Status: Still Failing Duration: 30 minutes and 0 seconds Commit: 55073d6 (trunk) Author: Alexandru Parvulescu Message: OAK-819 Lucene fulltext on node not working properly - marking failing tests

[Still Failing] apache/jackrabbit-oak#1535 (trunk - b30b873)

Build Update for apache/jackrabbit-oak - Build: #1535 Status: Still Failing Duration: 45 minutes and 56 seconds Commit: b30b873 (trunk) Author: Angela Schreiber Message: OAK-51 : Access Control Management (wip) git-svn-id:

[Fixed] apache/jackrabbit-oak#1539 (trunk - 9dc09b8)

Build Update for apache/jackrabbit-oak - Build: #1539 Status: Fixed Duration: 31 minutes and 14 seconds Commit: 9dc09b8 (trunk) Author: Angela Schreiber Message: OAK-527: permissions (wip, clean up) git-svn-id: