You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/04/09 01:36:46 UTC
[jira] Updated: (MNG-2483) Review caching strategies in
maven-project
[ http://jira.codehaus.org/browse/MNG-2483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-2483:
------------------------------
Fix Version/s: (was: 2.1.x)
2.1-alpha-1
Component/s: (was: Settings)
(was: Artifacts)
(was: Repositories)
(was: General)
(was: Sites & Reporting)
(was: Deployment)
(was: Dependencies)
(was: Performance)
(was: Reactor and workspace)
(was: Plugin Requests)
(was: Embedding)
(was: Ant tasks)
(was: Plugin API)
(was: maven-archiver)
(was: Logging)
(was: Plugin Creation Tools)
(was: Plugins and Lifecycle)
(was: Artifacts and Repositories)
Summary: Review caching strategies in maven-project (was: Review caching strategies throughout Maven for long-lived processes)
> Review caching strategies in maven-project
> ------------------------------------------
>
> Key: MNG-2483
> URL: http://jira.codehaus.org/browse/MNG-2483
> Project: Maven 2
> Issue Type: Improvement
> Components: Inheritance and Interpolation
> Affects Versions: 2.0.4, 2.0.5
> Reporter: John Casey
> Assignee: Jason van Zyl
> Priority: Critical
> Fix For: 2.1-alpha-1
>
>
> 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