[ 
https://issues.apache.org/jira/browse/SLING-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350199#comment-16350199
 ] 

ASF GitHub Bot commented on SLING-7466:
---------------------------------------

DominikSuess opened a new pull request #1: SLING-7466 - adding update of 
existing resource to make sure datauri …
URL: https://github.com/apache/sling-org-apache-sling-installer-core/pull/1
 
 
   …is clean

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> EntityResourceList cleaning up resource instead of updating
> -----------------------------------------------------------
>
>                 Key: SLING-7466
>                 URL: https://issues.apache.org/jira/browse/SLING-7466
>             Project: Sling
>          Issue Type: Bug
>          Components: Installer
>    Affects Versions: Installer Core 3.8.10
>            Reporter: Dominik Süß
>            Priority: Major
>             Fix For: Installer Core 3.8.12
>
>
> In case of a replaced launchpad containing an unchanged resource the 
> EntityResourceList is called for "addOrUpdate" of this Resource - in case the 
> resource already exists but the digest differs the method currently drops the 
> new resource without updating the existing one keeping the old dataUri.
> The issue manifests if these RegisteredResources are currently in INSTALL 
> state and the INSTALLED version gets dropped subsequently.
> This isn't just a theoretical case but was observed for cases where a bundle 
> in an n-1 version was patched to the same version provided in version n of 
> launchpad and launchpad hasn't changed for n+1. If the jcr version is then 
> removed the installation of the outdated registeredResource fails because of 
> a wrong dataUri.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to