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

Posted to issues@maven.apache.org by "Matt Nelson (Jira)" <ji...@apache.org> on 2022/01/18 23:21:00 UTC

[jira] [Commented] (MENFORCER-411) DependencyConvergence should support including/excluding certain dependencies

    [ https://issues.apache.org/jira/browse/MENFORCER-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17478263#comment-17478263 ] 

Matt Nelson commented on MENFORCER-411:
---------------------------------------

Would this introduce a false sense of correctness on a build that could then have later build failures caused by the compile/test classpaths or packaging order in the case of war/shade?

> 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)