Update detection might deleted copied artifact
----------------------------------------------
Key: SLING-2381
URL: https://issues.apache.org/jira/browse/SLING-2381
Project: Sling
Issue Type: Bug
Components: Installer
Affects Versions: Installer Core 3.3.2
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: Installer Core 3.3.4
The new update detection for artifacts introduced with SLING-2339 might lead to
a situation where the artifact can't be installed anymore.
This happens with providers where the artifact is first copied into the file
system like the jcr provider.
The situation can occur if the artifact has first been added through the
updateResources method and before this new artifact is processed, the provider
is restarted and reports the artifact again in the registerResources method.
This results in two InternalResource instances where the first one has a
pointer to the copied file. The second one does not get the pointer as the file
is already copied. However during the detection this file is removed as well as
the first instance. Therefore the second instance does not know the file
anymore.
We have to check for this explicitly in the registerResources method
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
