You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2007/02/28 18:37:48 UTC
[jira] Closed: (MNG-2483) Review caching strategies throughout
Maven for long-lived processes
[ http://jira.codehaus.org/browse/MNG-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl closed MNG-2483.
------------------------------
Resolution: Fixed
We have taken care of the case in maven-project. Each instance where we are doing this requires a new issue.
> Review caching strategies throughout Maven for long-lived processes
> -------------------------------------------------------------------
>
> Key: MNG-2483
> URL: http://jira.codehaus.org/browse/MNG-2483
> Project: Maven 2
> Issue Type: Improvement
> Components: Ant tasks, Artifacts, Artifacts and Repositories, Dependencies, Deployment, Embedding, General, Inheritance and Interpolation, Logging, maven-archiver, Performance, Plugin API, Plugin Creation Tools, Plugin Requests, Plugins and Lifecycle, Reactor and workspace, Repositories, Settings, Sites & Reporting
> Affects Versions: 2.0.4, 2.0.5
> Reporter: John Casey
> Assigned To: Jason van Zyl
> Priority: Critical
> Fix For: 2.1.x
>
>
> We need to revisit all instances where Maps, etc. are used to cache data inside Maven (maven-artifact has some, as does maven-project, f.e.). Wherever caching is used, we need to apply some sort of aging and/or size-limiting implementation to keep Maven from chewing up massive amounts of memory in long-lived processes, such as IDE extensions.
--
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