[ https://issues.apache.org/jira/browse/SLING-7991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominik Süß updated SLING-7991: ------------------------------- Description: 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. Additionally a mechanism to bake a start-order defined in feature properties during the merge process would be beneficial. Any who's start-order would need to be set to a specific value would need to declare the feature property "default.content.startorder" was: 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. > 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: 40m > 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. > Additionally a mechanism to bake a start-order defined in feature properties > during the merge process would be beneficial. Any who's start-order would > need to be set to a specific value would need to declare the feature property > "default.content.startorder" -- This message was sent by Atlassian JIRA (v7.6.3#76005)