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

Robert Scholte closed MENFORCER-332.
------------------------------------
      Assignee: Robert Scholte
    Resolution: Incomplete

With MENFORCER-277 the implementation has been replaced by Maven Dependency 
Graph.
As there is no project to compare the numbers, I have to close this ticket 
because it has become invalid: dependency-graph works different compared to 
dependency-tree.

> Performance regression in bannedDependencies rule
> -------------------------------------------------
>
>                 Key: MENFORCER-332
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-332
>             Project: Maven Enforcer Plugin
>          Issue Type: Bug
>          Components: Standard Rules
>    Affects Versions: 1.3, 1.4
>            Reporter: Richard Atkins
>            Assignee: Robert Scholte
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Since adding maven-dependency-tree as a dependency, bannedDependencies has 
> had a significant performance regression when it comes to building the 
> dependency tree to check. In a multi-module project with more than one 
> bannedDependencies rule defined, build times are significantly slower: one 
> project using over 100 modules and 20 bannedDependencies rules takes 10 mins 
> just to run maven validate, while using maven-enforcer-plugin 1.1.1 the build 
> time is only 1 min.
> The rule should be updated to cache the dependency tree for a project, and to 
> reuse it across rules for the same project. To support parallel builds 
> correctly, the cache will also have to support caching more than one 
> dependency tree at a time.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to