maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MENFORCER-213) big performance degradation after upgrade from 1.1 to 1.3.1
Date Fri, 16 Mar 2018 22:40:28 GMT

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

Michael Osipov closed MENFORCER-213.
------------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If
you think this issue still applies, retest your problem with the most recent version of Maven
and the affected component, reopen and post your results.

> big performance degradation after upgrade from 1.1 to 1.3.1
> -----------------------------------------------------------
>
>                 Key: MENFORCER-213
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-213
>             Project: Maven Enforcer Plugin
>          Issue Type: Improvement
>          Components: Plugin
>    Affects Versions: 1.3.1
>         Environment: mvn 3.0.5, MacOsX yosemite, SSD disk
>            Reporter: Milos Kleint
>            Priority: Major
>         Attachments: 2014-11-13_0851.png, 2014-11-13_0852.png, enforcer-1.1.nps, enforcer-1.1.png,
enforcer-1.3.1.nps, enforcer-1.3.1.png
>
>
> mvn validate on our big codebase (142 modules) with 1.1 enforcer - 30.090s
> mvn validate with (1.3.1 enforcer) - 2:20.074s
> only enforcer plugin executions happen, bannedDependencies rules
> both times are on my laptop with profiler snapshot collection turned on.
> with the 1.3.1 it's obvious that the majority of time is indeed spent in the dependency
graph codebase that is missing from 1.1.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message