[
https://issues.apache.org/jira/browse/SLING-13291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michał Wędzik updated SLING-13291:
----------------------------------
Description:
The repo-init conflict validator can report a false-positive conflict when the
first primaryType in a create-path definition differs, even though the
statements do not represent a real path-type conflict.
This change adjusts conflict detection logic so that this first-primaryType
case is handled correctly and warnings are emitted only for real conflicts on
matching paths
was:Expose a getter for conflicts in ValidationReport to enable more reliable
conflict removal in the aemanalyser-maven-plugin.
> Fix false-positive repo-init conflict detection when first primaryType differs
> ------------------------------------------------------------------------------
>
> Key: SLING-13291
> URL: https://issues.apache.org/jira/browse/SLING-13291
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
> Reporter: Michał Wędzik
> Assignee: Michał Wędzik
> Priority: Major
>
> The repo-init conflict validator can report a false-positive conflict when
> the first primaryType in a create-path definition differs, even though the
> statements do not represent a real path-type conflict.
> This change adjusts conflict detection logic so that this first-primaryType
> case is handled correctly and warnings are emitted only for real conflicts on
> matching paths
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
