You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark Crocker (JIRA)" <ji...@codehaus.org> on 2008/10/18 01:55:19 UTC
[jira] Commented: (MNG-3222) Compile dependency resolution is slow
[ http://jira.codehaus.org/browse/MNG-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151195#action_151195 ]
Mark Crocker commented on MNG-3222:
-----------------------------------
A posting on Nabble suggested using:
<dependencyLocationsEnabled>false</dependencyLocationsEnabled>
as a work-around.
See: http://www.nabble.com/Dependency-Report-Taking-Forever-And-A-Day-td19416718.html
> Compile dependency resolution is slow
> -------------------------------------
>
> Key: MNG-3222
> URL: http://jira.codehaus.org/browse/MNG-3222
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.4
> Reporter: Stefan Behnel
> Fix For: 2.0.x
>
>
> Compile dependency resolution is slow. I just wrote an empty module (only test sources that were not compiled), and it took Maven more than five minutes to build it, without any compilation/generation/testing/whatsoever. I just took literally minutes to resolve a couple of hundred compile time dependencies for the compiler plugin, which was then executed twice.
> To me, this sounds like a problem with the algorithmic complexity of the dependency resolution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira