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 02:23:46 UTC
[jira] Reopened: (MNG-2481) project builder should make the
processed project cache configurable
[ http://jira.codehaus.org/browse/MNG-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter reopened MNG-2481:
-------------------------------
> project builder should make the processed project cache configurable
> --------------------------------------------------------------------
>
> Key: MNG-2481
> URL: http://jira.codehaus.org/browse/MNG-2481
> Project: Maven 2
> Issue Type: Bug
> Components: Performance, POM
> Affects Versions: 2.0.4
> Reporter: Brett Porter
>
> the cache in the project builder is a simple map. This is usually fine for Maven, but in long lived processes (Continuum, MRM, and I imagine the IDE plugins as it gets used more) it can chew up quite some memory.
> I'd suggest we make it configurable:
> - can turn it on or off using plexus configuration
> - can limit its size using plexus configuration
> - can change other options, such as adding expiry ages to items regardless of size
> Rather than implementing something in the project builder itself, I suggest having a cache plexus component that does everything we need it to (this could be reused in the webapps as well). I'm not sure of any existing caching solutions (I know OSCache has a general Java cache but don't know how suitable it is). One alterantive might be to round out commons-cache with some features and plexus descriptors.
--
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