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 2018/10/09 07:19:00 UTC

[jira] [Comment Edited] (SLING-7991) Make packages part of last execution plan if no start-order is defined

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

Dominik Süß edited comment on SLING-7991 at 10/9/18 7:18 AM:
-------------------------------------------------------------

https://github.com/apache/sling-whiteboard/pull/19 for patch


was (Author: dsuess):
https://github.com/apache/sling-whiteboard/pull/18 for patch

> Make packages part of last execution plan if no start-order is defined
> ----------------------------------------------------------------------
>
>                 Key: SLING-7991
>                 URL: https://issues.apache.org/jira/browse/SLING-7991
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>            Reporter: Dominik Süß
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> SLING-7871 introduces a mechanism that installs content-packages in one or more execution plans for a deterministic, layer-able install sequence (consumer adding a subsequent layer of installables via additional features guaranteed to be processed later). 
> As by default the start-order is set to 0 by default a feature may not define a position earlier then the ones without start-order. 
> As the installation sequence may be crucial due to the hierarchical dependencies packages without start-order defined should rather be installed as last which only mandates setting a start-order on the lower layers while not setting a start-order on leaf packages won't do any harm.



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