[
https://jira.codehaus.org/browse/MDEP-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ZILVINAS VILUTIS updated MDEP-404:
----------------------------------
Attachment: dep-tree-maven-3.0.5.log
dep-tree-maven-2.2.1.log
Still significant difference exists, please see logs:
[^dep-tree-maven-2.2.1.log] - takes 13s using maven 2.2.1
[^dep-tree-maven-3.0.5.log] - takes 55s using maven 3.0.5
> mvn 3.0.4 is extreemly slow with a large number of "import" dependencies.
> -------------------------------------------------------------------------
>
> Key: MDEP-404
> URL: https://jira.codehaus.org/browse/MDEP-404
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: tree
> Affects Versions: 2.4
> Environment: Linux skhalipau.internal.corp 3.2.0-32-generic
> #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Siarhei Khalipau
> Attachments: dep-tree-maven-2.2.1.log, dep-tree-maven-3.0.5.log,
> jprofiler_mvn_dependency_tree.tar.bz2, mvn_2.2.1_dependency_tree.log,
> mvn_3.0.4_dependency_tree.log, stacktrace.txt
>
>
> In comparison with maven 2.2.1 resolving of dependencies with scope "import"
> is very slow in maven 3.
> Example results for "mvn dependency:tree" in one my project: maven 2.2.1 says
> "[INFO] Total time: 8 seconds" but 3.0.4 "[INFO] Total time: 13:02.069s".
> Resulting trees are identical.
> I profiled the code and found that maven 3 did not cache parsed pom files but
> it reads and parses one pom file every time when it find it in imported
> dependencies. So the method
> org.apache.maven.model.building.DefaultModelBuilder.importDependencyManagement()
> is called many times for one artifact. There is JProfiler result for "mvn
> dependency:tree" in attachment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
