You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/04/20 08:33:58 UTC

[jira] [Closed] (SLING-4632) File installer does not support moving Sling directory

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

Carsten Ziegeler closed SLING-4632.
-----------------------------------

> File installer does not support moving Sling directory
> ------------------------------------------------------
>
>                 Key: SLING-4632
>                 URL: https://issues.apache.org/jira/browse/SLING-4632
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: File Installer 1.0.4
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: File Installer 1.1.0
>
>
> The file installer uses the full path to the install folder as a hash as the schema to be passed to the installer. The schame is used on a restart to detect that this is the same installation location.
> If now the whole Sling home is moved to a different location, this results in a different absolute path for the install directory. On a restart, the install directory is detected as a new location. As the OSGi installer by design does not touch unknown/stale locations, this results in the old resources being available, together with the new ones. Which results in hard to trace/find problems once something is changed in the install folder.
> We have to use new full path and not just the directory, otherwise if the installer is configured with two directories having the same name, this would result in a clash.
> If an absolute path is configured for the installer, it's totally fine to use the full path. The only problem are relative paths to sling.home
> A solution is to check whether the path starts with sling.home and then replace it with ${sling.home} instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)