You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Nigel Magnay (JIRA)" <ji...@codehaus.org> on 2006/12/27 11:20:09 UTC
[jira] Created: (MNG-2717) Cache the repo dependencies
Cache the repo dependencies
---------------------------
Key: MNG-2717
URL: http://jira.codehaus.org/browse/MNG-2717
Project: Maven 2
Issue Type: Improvement
Components: Artifacts, Bootstrap & Build, Dependencies
Affects Versions: 2.0.4
Reporter: Nigel Magnay
Priority: Minor
Once projects get of a significant size, there can be a large number of dependencies, and transitive dependencies thereof.
In our WAR projects (for example), this can approach a few hundred dependencies (though there are a fair number of duplicates).
Looking at JProfiler (after examinining one of my own non-maven tools that also parses POM files), the parsing cycle of reading all these POM files from the local repo, and pull-parsing them for dependencies takes a significant proportion of the execute time (4 of the top 10 hotspots are in MXParser.
Since non-snapshot dependencies ought never to change their dependencies [1], and dependency download could trigger the fact that the dependencies might have changed anyway, some kind of caching mechanism could be used to speed this up (something like {artifact, scope} -> List{artifact}).
[1] I have reserved a particular space in hell for those people who *do* change the deps on released POMs... ;-S
--
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
[jira] Closed: (MNG-2717) Cache the repo dependencies
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-2717.
-----------------------------
Resolution: Won't Fix
Fix Version/s: (was: 3.x)
changing to won't fix since I don't think this specific solution was implemented, it's just not necessary any more
> Cache the repo dependencies
> ---------------------------
>
> Key: MNG-2717
> URL: http://jira.codehaus.org/browse/MNG-2717
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Nigel Magnay
> Priority: Minor
>
> Once projects get of a significant size, there can be a large number of dependencies, and transitive dependencies thereof.
> In our WAR projects (for example), this can approach a few hundred dependencies (though there are a fair number of duplicates).
> Looking at JProfiler (after examinining one of my own non-maven tools that also parses POM files), the parsing cycle of reading all these POM files from the local repo, and pull-parsing them for dependencies takes a significant proportion of the execute time (4 of the top 10 hotspots are in MXParser.
> Since non-snapshot dependencies ought never to change their dependencies [1], and dependency download could trigger the fact that the dependencies might have changed anyway, some kind of caching mechanism could be used to speed this up (something like {artifact, scope} -> List{artifact}).
> [1] I have reserved a particular space in hell for those people who *do* change the deps on released POMs... ;-S
--
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
[jira] Updated: (MNG-2717) Cache the repo dependencies
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MNG-2717:
---------------------------
Fix Version/s: (was: Reviewed Pending Version Assignment)
2.1
> Cache the repo dependencies
> ---------------------------
>
> Key: MNG-2717
> URL: http://jira.codehaus.org/browse/MNG-2717
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Nigel Magnay
> Priority: Minor
> Fix For: 2.1
>
>
> Once projects get of a significant size, there can be a large number of dependencies, and transitive dependencies thereof.
> In our WAR projects (for example), this can approach a few hundred dependencies (though there are a fair number of duplicates).
> Looking at JProfiler (after examinining one of my own non-maven tools that also parses POM files), the parsing cycle of reading all these POM files from the local repo, and pull-parsing them for dependencies takes a significant proportion of the execute time (4 of the top 10 hotspots are in MXParser.
> Since non-snapshot dependencies ought never to change their dependencies [1], and dependency download could trigger the fact that the dependencies might have changed anyway, some kind of caching mechanism could be used to speed this up (something like {artifact, scope} -> List{artifact}).
> [1] I have reserved a particular space in hell for those people who *do* change the deps on released POMs... ;-S
--
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
[jira] Reopened: (MNG-2717) Cache the repo dependencies
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter reopened MNG-2717:
-------------------------------
> Cache the repo dependencies
> ---------------------------
>
> Key: MNG-2717
> URL: http://jira.codehaus.org/browse/MNG-2717
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Nigel Magnay
> Priority: Minor
>
> Once projects get of a significant size, there can be a large number of dependencies, and transitive dependencies thereof.
> In our WAR projects (for example), this can approach a few hundred dependencies (though there are a fair number of duplicates).
> Looking at JProfiler (after examinining one of my own non-maven tools that also parses POM files), the parsing cycle of reading all these POM files from the local repo, and pull-parsing them for dependencies takes a significant proportion of the execute time (4 of the top 10 hotspots are in MXParser.
> Since non-snapshot dependencies ought never to change their dependencies [1], and dependency download could trigger the fact that the dependencies might have changed anyway, some kind of caching mechanism could be used to speed this up (something like {artifact, scope} -> List{artifact}).
> [1] I have reserved a particular space in hell for those people who *do* change the deps on released POMs... ;-S
--
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
[jira] Closed: (MNG-2717) Cache the repo dependencies
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-2717.
------------------------------
Resolution: Fixed
> Cache the repo dependencies
> ---------------------------
>
> Key: MNG-2717
> URL: http://jira.codehaus.org/browse/MNG-2717
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Nigel Magnay
> Priority: Minor
> Fix For: 3.x
>
>
> Once projects get of a significant size, there can be a large number of dependencies, and transitive dependencies thereof.
> In our WAR projects (for example), this can approach a few hundred dependencies (though there are a fair number of duplicates).
> Looking at JProfiler (after examinining one of my own non-maven tools that also parses POM files), the parsing cycle of reading all these POM files from the local repo, and pull-parsing them for dependencies takes a significant proportion of the execute time (4 of the top 10 hotspots are in MXParser.
> Since non-snapshot dependencies ought never to change their dependencies [1], and dependency download could trigger the fact that the dependencies might have changed anyway, some kind of caching mechanism could be used to speed this up (something like {artifact, scope} -> List{artifact}).
> [1] I have reserved a particular space in hell for those people who *do* change the deps on released POMs... ;-S
--
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
[jira] Commented: (MNG-2717) Cache the repo dependencies
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204279#action_204279 ]
Jason van Zyl commented on MNG-2717:
------------------------------------
Performance is improved in 3.x. We've been profiling and have hooked up performance tests.
> Cache the repo dependencies
> ---------------------------
>
> Key: MNG-2717
> URL: http://jira.codehaus.org/browse/MNG-2717
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Affects Versions: 2.0.4
> Reporter: Nigel Magnay
> Priority: Minor
> Fix For: 3.x
>
>
> Once projects get of a significant size, there can be a large number of dependencies, and transitive dependencies thereof.
> In our WAR projects (for example), this can approach a few hundred dependencies (though there are a fair number of duplicates).
> Looking at JProfiler (after examinining one of my own non-maven tools that also parses POM files), the parsing cycle of reading all these POM files from the local repo, and pull-parsing them for dependencies takes a significant proportion of the execute time (4 of the top 10 hotspots are in MXParser.
> Since non-snapshot dependencies ought never to change their dependencies [1], and dependency download could trigger the fact that the dependencies might have changed anyway, some kind of caching mechanism could be used to speed this up (something like {artifact, scope} -> List{artifact}).
> [1] I have reserved a particular space in hell for those people who *do* change the deps on released POMs... ;-S
--
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