[
https://issues.apache.org/jira/browse/JCR-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572187#action_12572187
]
Alexander Klimetschek commented on JCR-1412:
--------------------------------------------
Yes, for a final new feature applied to the trunk I would modify the Config
classes directly.
My intention was to not modify core code in a maintenance branch and work
around to add it to the test code instead. That large volume only affects the
test cases.
I could have done it with repository.xml files, but I wanted to do a proof of
concept for a dynamic configuration, something I was missing for Jackrabbit
independent from JCR-1400.
> [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.
