You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Dominik Süß (JIRA)" <ji...@apache.org> on 2019/01/17 11:49:00 UTC

[jira] [Created] (SLING-8222) Statushandling of executionplans misses out behavior of content-extension on restarts

Dominik Süß created SLING-8222:
----------------------------------

             Summary: Statushandling of executionplans misses out behavior of content-extension on restarts
                 Key: SLING-8222
                 URL: https://issues.apache.org/jira/browse/SLING-8222
             Project: Sling
          Issue Type: Bug
          Components: Feature Model
            Reporter: Dominik Süß
            Assignee: Dominik Süß


The test case for the executionplan status doesn't reflect reality of restart behavior. As soon as the package registry is being reused the ExecutionPlanBuilder will already consider the packages as being installed and will not add further items to the execution plan - therefore the hashes will not be the same.

This ticket is about reducing the state handling to optional skipping if execution plans are the same (e.g restart without content-extension active) but just progressing as if no state is available yet and capturing the new state in case cached hashes are different (along with an info message).



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