[
https://jira.codehaus.org/browse/MENFORCER-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358760#comment-358760
]
Karl-Heinz Marbaise commented on MENFORCER-213:
-----------------------------------------------
Maybe i misunderstand a thing here but on the left side (*0851) i only see
EnforcerMojo.execute() afterwards i see getConfiguredMojo()...but i don't see
any hint about banDependencies()...or any other class related to the mentioned
rules...
On the other side (right) i see AbstractBanDependencies class and afterwards i
see a class "com.atlassian.maven.enforcer.BanVersionDeps" which i know is not
part of maven-enforcer/rules etc. ?
> big performance degradation after upgrade from 1.1 to 1.3.1
> -----------------------------------------------------------
>
> Key: MENFORCER-213
> URL: https://jira.codehaus.org/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
> Attachments: 2014-11-13_0851.png, 2014-11-13_0852.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
(v6.1.6#6162)
