jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-224) Allow the ContentRepositoryImpl to receive a CommitEditor in the constructor
Date Fri, 03 Aug 2012 10:09:02 GMT

    [ https://issues.apache.org/jira/browse/OAK-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13427954#comment-13427954
] 

Jukka Zitting commented on OAK-224:
-----------------------------------

+1 Looks like a good step forward.

FWIW I don't think all of the tests leveraging RepositoryTestUtils or otherwise creating a
ContentRepositoryImpl with the full set of editors and validators really need all those components
to be present. Ideally a *unit* test should run with as little extra code as possible, only
in integration tests should we have all those extra components enabled.
                
> Allow the ContentRepositoryImpl to receive a CommitEditor in the constructor
> ----------------------------------------------------------------------------
>
>                 Key: OAK-224
>                 URL: https://issues.apache.org/jira/browse/OAK-224
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Alex Parvulescu
>         Attachments: OAK-224.patch
>
>
> Following OAK-154 WIP, I'd like to tweak the ContentRepositoryImpl's constructor to receive
a CommitEditor.
> This will allow us to turn the Lucene dependency back to optional.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message