[
https://issues.apache.org/jira/browse/SLING-11838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-11838.
-------------------------------------
Resolution: Fixed
PR merged, thanks for the contribution [~dsuess]!
> Unexpected runmode inheritance behavior
> ---------------------------------------
>
> Key: SLING-11838
> URL: https://issues.apache.org/jira/browse/SLING-11838
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
> Reporter: Dominik Süß
> Assignee: Dominik Süß
> Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.3.2
>
>
> The current behavior how runmodes are evaluated for targeting the right
> feature model is counterintuitive and can lead to dependency bugs.
> Right now only the location within the direct package is evaluated but if a
> package is embedded within a package with a specific runmode that leads to
> problems:
> a) the expectation that everything within an e.g. install.author folder only
> applies to the author runmode is broken as install folders without author
> would target the generic model
> b) the implicit dependencies that are made explicit by the converter are
> broken an embedded package may be broken as a package of a generic install
> folder that's nested in a runmode specific install folder within a nesting
> package would have a dependency on a package not launched (and therefore
> fails the analyser checks)
> As some people may have established some implicit dependency on this behavior
> the goal for a fix is to provide a "legacy" mode and log the scenarios to be
> able to to track usages and evaluate the impact and only switch on a
> corresponding inheritance policy when this switch can be considered safe.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
