[
https://issues.apache.org/jira/browse/SLING-8222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Schaefer updated SLING-8222:
------------------------------------
Fix Version/s: JCR Package Init 1.0.0
> Statushandling of executionplans in PackageInit 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üß
> Priority: Major
> Fix For: JCR Package Init 1.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
