[
https://issues.apache.org/jira/browse/SLING-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001486#comment-13001486
]
Felix Meschberger commented on SLING-2013:
------------------------------------------
Rev. 1076292 : Unless sling.repository.home and/or
sling.repository.config.file.url framework properties are set the initial
configuration is stripped down to not contain the config URL and the home
parameter being relative to be resolved against sling.home.
Thus, in a default setup there is no absolute path stored in the configuration
any more.
> When creating the initial configuration use relative path names for the
> repository configuration and home
> ---------------------------------------------------------------------------------------------------------
>
> Key: SLING-2013
> URL: https://issues.apache.org/jira/browse/SLING-2013
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Jackrabbit Server 2.1.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: JCR Jackrabbit Server 2.1.2
>
>
> The Jackrabbit server creates a configuration on initial startup if none is
> available from the Configuration Admin service. This configuration will
> contain absolute path names to the repository configuration file as well as
> the repository home directory. This makes it hard to relocate the Sling Home
> folder because the configuration will still point to the old location.
> Instead the default configuration (unless overwritten by some framework
> property) should use relative path names to be resolved against sling.home
> once the repository is started/created.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
