You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Patrick Decat (JIRA)" <ji...@codehaus.org> on 2013/02/28 19:50:53 UTC

[jira] (MNG-5367) mvn 3.0.4 is extreemly slow with a large number of "import" dependencies.

    [ https://jira.codehaus.org/browse/MNG-5367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320635#comment-320635 ] 

Patrick Decat commented on MNG-5367:
------------------------------------

Same issue with Maven 3.0.3 & 3.0.4 and maven-dependency-plugin 2.4.
Fixed with maven-dependency-plugin 2.5 & 2.6.
                
> mvn 3.0.4 is extreemly slow with a large number of "import" dependencies.
> -------------------------------------------------------------------------
>
>                 Key: MNG-5367
>                 URL: https://jira.codehaus.org/browse/MNG-5367
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Dependencies
>    Affects Versions: 3.0.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: 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