We have quite a few caches all over the place in our code base (and some in plexus), quite a lot of them caching stuff based on this or that class (or method).
Almost all of them leak class references, as far as I can understand bloating permgen requirements (and hence memory usage) of maven. Most of these cache would seem to be relevant at the "MavenExecution" level, i.e. we could choose to ditch all of this at the end of each build without loosing any real performance. Quite a few of these caches use various "weak" type references but as far as I can see all of them are flawed and still leak ;) It would seem to me like we could use some kind of injectable cache scope that could be used, preferably bound to each execution. Anyone have any ideas on how we could do this ? Kristian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
