You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2018/11/22 17:40:00 UTC
[jira] [Assigned] (SLING-8128) Consistent ordering of sections when
merging features
[ https://issues.apache.org/jira/browse/SLING-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler reassigned SLING-8128:
---------------------------------------
Assignee: Carsten Ziegeler
> Consistent ordering of sections when merging features
> -----------------------------------------------------
>
> Key: SLING-8128
> URL: https://issues.apache.org/jira/browse/SLING-8128
> Project: Sling
> Issue Type: Bug
> Components: Feature Model, Maven Plugins and Archetypes
> Reporter: Robert Munteanu
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: slingfeature-maven-plugin 1.0.0
>
>
> It seems to me that when merging feature files the order in which the content of sections is included is not consistent.
> It seems that, for instance, if I define an aggregate feature the definition order is not respected and the {{repoinit}} section is not ordered correctly.
> This is most visible with repoinit since incorrect ordering leads to failures at runtime, e.g.
> - feature 1 creates /apps
> - features 2 sets ACL on /apps
> If the order is not respected, the startup will fail.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)