[
https://issues.apache.org/jira/browse/MNG-6760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069876#comment-17069876
]
Hudson commented on MNG-6760:
-----------------------------
Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4
See
https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/
> [REGRESSION] ExclusionArtifactFilter result invalid when wildcard exclusion
> is followed by other exclusions
> -----------------------------------------------------------------------------------------------------------
>
> Key: MNG-6760
> URL: https://issues.apache.org/jira/browse/MNG-6760
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.6.2
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Major
> Fix For: 3.6.3
>
>
> MNG-6713 was a fix to support wildcard exclusions. Before they were always
> ignored, since it was an exact match of the wildcard with the groupId or
> artifactId, which would always be false.
> The improvement contains a bug, because in case of a wildcard, it does a
> direct match, ignoring following exclusions.
> *WORKAROUND*: Start the exclusion-list with the explicit groupID and
> artifactId, ending with the exclusions containing wildcards. This will
> restore the behavior as before MNG-6713
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
