You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2008/02/25 20:40:51 UTC

[jira] Updated: (JCR-1412) [Patch] Java-based test configuration of Jackrabbit (no repository.xml needed)

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

Jukka Zitting updated JCR-1412:
-------------------------------

    Priority: Minor  (was: Major)
     Summary: [Patch] Java-based test configuration of Jackrabbit (no repository.xml needed)  (was: [Patch] Pure Java-based configuration of Jackrabbit (no repository.xml needed))

ACK. I update the title to better reflect that this is a test-only feature for now.

I'm OK with having this in 1.3.4 since it's a special release anyhow, but generally we should avoid introducing extra features in maintenance branches, especially if a similar feature doesn't already exist in trunk.

> [Patch] Java-based test 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
>            Priority: Minor
>             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.