[jira] [Resolved] (SLING-8128) Consistent ordering of sections when merging features

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-8128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-8128.
-------------------------------------
    Resolution: Fixed

I've fixed this by recording the ordering of the setXYZ calls. Please note that you can put an exclude for files at any place, but it's always applied to all file includes.

> 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)