[
https://issues.apache.org/jira/browse/JCR-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572182#action_12572182
]
Jukka Zitting commented on JCR-1412:
------------------------------------
Instead of adding builder classes I'd rather just modify the Config classes
directly.
Also, I'm a bit reluctant to add such a large volume of stuff in a maintenance
branch. Is this required for JCR-1400 or could you live without it? Couldn't
you just create custom repository.xml files for each test case that needs
custom configuration?
> [Patch] Pure Java-based configuration of Jackrabbit (no repository.xml needed)
> ------------------------------------------------------------------------------
>
> Key: JCR-1412
> URL: https://issues.apache.org/jira/browse/JCR-1412
> Project: Jackrabbit
> Issue Type: New Feature
> Components: config, jackrabbit-core, test
> Reporter: Alexander Klimetschek
> Fix For: 1.3.4
>
> Attachments: jackrabbit-core.dynamic-config-for-testing.patch
>
>
> Jackrabbit should be dynamically configurable, ie. without the need for a
> repository.xml but through pure Java code.
> This is helpful for unit tests, where you want to automatically test
> different configurations (eg. PersistenceManagers) without creating hundreds
> of repository.xml files that differ only in certain parts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
