You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Julian Sedding (Jira)" <ji...@apache.org> on 2024/11/28 15:03:00 UTC

[jira] [Resolved] (SLING-12508) CheckRequirementsCapabilities should support cardinality multiple

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

Julian Sedding resolved SLING-12508.
------------------------------------
    Resolution: Fixed

> CheckRequirementsCapabilities should support cardinality multiple
> -----------------------------------------------------------------
>
>                 Key: SLING-12508
>                 URL: https://issues.apache.org/jira/browse/SLING-12508
>             Project: Sling
>          Issue Type: Bug
>          Components: Feature Model Analyser
>    Affects Versions: Feature Model Analyser 2.0.10
>            Reporter: Julian Sedding
>            Assignee: Julian Sedding
>            Priority: Minor
>             Fix For: Feature Model Analyser 2.0.12
>
>
> This issue was first reported for the [aemanalyser-maven-plugin|https://github.com/adobe/aemanalyser-maven-plugin/issues/306]. However, the root cause is in the {{CheckRequirementsCapabilities}} implementation, which warns when more than one matching capability is found, regardless of the requirement's cardinality.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)