[
https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15732716#comment-15732716
]
Alexander Klimetschek commented on SLING-5745:
----------------------------------------------
Unfortunately we could not find any hint on what was going wrong. Only thing
was that we had 4.1.0-snapshot bundles before and went to a 4.1.0 release,
however, the entire tree was replaced in the package and both jars never were
present at the same time in the JCR. In many cases it works fine.
IIUC, the installer logic is pretty complex. Until it's 100% perfect, a "Reset
cache" operation seems useful. Sometimes getting things to work is more time
critical than understanding it fully.
> Provide a button to clear all registered entities and reinstall those
> ---------------------------------------------------------------------
>
> Key: SLING-5745
> URL: https://issues.apache.org/jira/browse/SLING-5745
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: Installer Console 1.0.2
> Reporter: Konrad Windszus
>
> Currently the web console at {{/system/console/osgi-installer}} exposes the
> history/state of the OSGi installer. In case the state is not reflecting
> reality for some reason, there should be a possibility to remove that history
> and restart the according bundles with a button inside that console.
> The actions which should be triggered under the hood should be
> # remove the data file {{RegisteredResourceList.ser}}
> # restart the bundle {{org.apache.sling.installer.core}}
> That should lead to every provider being asked about all entities which are
> then processed again so you end up with state again where the most
> prioritized entites are deployed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
