[jira] [Resolved] (OAK-5656) InitialContent depends on document.bundlor.BundlingConfigInitializer

["Marcel Reutegger (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OAK-5656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved OAK-5656.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.8

Applied patch to trunk: http://svn.apache.org/r1808312

> InitialContent depends on document.bundlor.BundlingConfigInitializer
> --------------------------------------------------------------------
>
>                 Key: OAK-5656
>                 URL: https://issues.apache.org/jira/browse/OAK-5656
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: angela
>            Assignee: Marcel Reutegger
>            Priority: Minor
>              Labels: modularization, tech-debt
>             Fix For: 1.8, 1.7.8
>
>         Attachments: OAK-5656.patch, OAK-5656.patch
>
>
> [~chetanm], in the light of OAK-4975 a dependency to the document nodestore code got introduced in {{org.apache.jackrabbit.oak.plugins.nodetype.write.InitialContent}} by adding the following line:
> {code}
>         BundlingConfigInitializer.INSTANCE.initialize(builder);
> {code}
> the {{BundlingConfigInitializer}} is defined in the {{org.apache.jackrabbit.oak.plugins.document.bundlor}}.
> To me that looks quite troublesome and I don't think the generic JCR-InitialContent should have any dependency on the document nodestore code base.
> Why not defining a dedicated {{RepositoryInitializer}} for that kind of init an making sure it is listed in the (default) setup scenarios (or at least in those that actually have a document store and thus require this)?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)