[jira] (MRM-1774) RepositoryAdminException when configuring a custom JCR repository path

["Mario Steinhoff (JIRA)" <ji...@codehaus.org>]

Mario Steinhoff created MRM-1774:
------------------------------------

             Summary: RepositoryAdminException when configuring a custom JCR repository path
                 Key: MRM-1774
                 URL: https://jira.codehaus.org/browse/MRM-1774
             Project: Archiva
          Issue Type: Bug
    Affects Versions: 1.4-M4
         Environment: Debian 6.0.7 kernel 2.6.32-5-686
OpenJDK 1.6.0_18
tomcat 6.0.35
            Reporter: Mario Steinhoff
         Attachments: archiva-error.log

This is a standard debian tomcat install where the tomcat user does not have write access to the tomcat folder itself. All archiva data is placed on a separate partition at /mnt/datastore1/archiva.

When I try to configure an alternative jackrabbit repository location as described [here|http://archiva.apache.org/docs/1.4-M4/adminguide/repositories-content-storage.html] by setting the jcr-config's constructor-arg to my custom path, the jackrabbit repository is created but the following exception shows up in the archiva.log:

{code}org.apache.archiva.admin.model.RepositoryAdminException: Cannot create directory: /var/lib/tomcat6/data/remotes/central/.index{code}

I tried to grep for '/data' in the war folder but haven't found anything except the jcr repository part. Where does this path come from?

I currently have created a symlink that points to the archiva data location which works fine but I don't like this solution because now I have to maintain configuration at multiple locations (symlink+config files).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira