[
https://issues.apache.org/jira/browse/MENFORCER-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17478947#comment-17478947
]
Matt Nelson commented on MENFORCER-411:
---------------------------------------
{quote}Can you give an example of how there would be a later build failure from
one of the causes you mentioned?{quote}
Maven has deterministic class path ordering[1]. Introducing an option to ignore
convergence errors on specific dependencies could introduce build failures if
the pom is reordered or sorted. In this scenario the error would be later in
the build (compile or test) and it would not be as immediately clear that it is
a convergence error.
[1]
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Transitive_Dependencies
> DependencyConvergence should support including/excluding certain dependencies
> -----------------------------------------------------------------------------
>
> Key: MENFORCER-411
> URL: https://issues.apache.org/jira/browse/MENFORCER-411
> Project: Maven Enforcer Plugin
> Issue Type: Improvement
> Components: Standard Rules
> Affects Versions: 3.0.1
> Reporter: Forrest Feaser
> Priority: Major
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> It would be nice if the DependencyConvergence rule could specify certain
> dependencies that should/should not fail the build. This might be useful if
> your project has a lot of dependency conflicts, but you know there are just a
> few troublesome ones that cause issues, and you don't want to resolve the
> conflicts for your entire project.
> Here is my PR: https://github.com/apache/maven-enforcer/pull/136
> Do I need to sign the Contributor License Agreement for this?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
