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 2011/05/20 08:34:47 UTC
[jira] [Reopened] (SLING-2031) Use bundle location to create path
for persisting new configurations
[ https://issues.apache.org/jira/browse/SLING-2031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler reopened SLING-2031:
-------------------------------------
Thinking about this, this seems more like a bad idea as this scatters the configs around the repository. Especially with bundle updates and uninstalls this becomes overly complicated
> Use bundle location to create path for persisting new configurations
> --------------------------------------------------------------------
>
> Key: SLING-2031
> URL: https://issues.apache.org/jira/browse/SLING-2031
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: Installer Core 3.1.2, JCR Installer 3.0.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: Installer Core 3.2.0, JCR Installer 3.1.0
>
>
> As suggested by Tobi in SLING-1971:
> "can the path be guessed from the respective bundle location? e.g. if the bundle location is /apps/myapp/install/abc-1.0.jar, the config should go to /apps/myapp/config/..."
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira