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

Forrest Feaser updated MENFORCER-411:
-------------------------------------
    Description: 
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:

Do I need to sign the Contributor License Agreement for this?

  was:
It would be nice if the standard RequireSameVersions rule could search 
transitive dependencies. This might be useful if your project has a lot of 
transitive dependency conflicts, but you know there are just a few troublesome 
dependencies that cause issues, and you don't want to resolve the conflicts for 
your entire project using the DependencyConvergence rule. Alternatively, the 
DependencyConvergence rule could accept a list of dependencies to 
include/exclude.

Is there a reason why this isn't already supported?

Here is my PR: [https://github.com/apache/maven-enforcer/pull/135]

Do I need to sign the Contributor License Agreement for this?

        Summary: DependencyConvergence should support including/excluding 
certain dependencies  (was: RequireSameVersions should search 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:
> Do I need to sign the Contributor License Agreement for this?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to