[OAK-5656] InitialContent depends on document.bundlor.BundlingConfigInitializer

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.7.8, 1.8.0
• Component/s: core
• Labels: modularization tech-debt
• Epic Link: Modularisation of Oak
• Assignee: Marcel Reutegger
• Reporter: Angela Schreiber
• Created: 14/Feb/17 15:29
• Updated: 29/Sep/17 10:09
• Resolved: 14/Sep/17 06:30

Description

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:

        BundlingConfigInitializer.INSTANCE.initialize(builder);

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)?