maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Greenberg (JIRA)" <>
Subject [jira] Commented: (MNG-3472) configuration possibilities to limit size of local repository
Date Mon, 10 Nov 2008 16:16:13 GMT


David Greenberg commented on MNG-3472:

Andrus is right.  The local repository is fundamentally tied to the Maven tool; therefore,
Maven should manage it.  A plugin would do the job, but I think there is more to this than
simply scrubbing the repository periodically.  I would be concerned that cleaning the local
repo would eventually slow down builds.  After all, why have a local repo if it doesn't make
the build process more efficient?  What would be really great is a way for Maven to determine
which dependencies are used most often.  Then, it could keep those while cleaning up the rest.
 Whatever extension to Maven that does this should clean the repo before downloading any new
files.  That way, when a critical bug fix needs to be built and tested, the developer or build
server is not waiting forever for the local repo sweep to finish.  It may make each build
just slightly longer, but it would prevent bottlenecks.

Just my two cents...and I understand that I should just build it instead of complaining about
it.  I'll see what I can do.

> configuration possibilities to limit size of local repository
> -------------------------------------------------------------
>                 Key: MNG-3472
>                 URL:
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Settings
>    Affects Versions: 2.0.8
>            Reporter: manuel aldana
> it would be great to make repository-size configurable, for instance by setting the maximum
number of downloads of a snapshot-version to be kept. thus the explosion of local repository
size can be reduced.
> especially when you are working with many in-house multi-module projects which are marked
as snapshots before released , can increase repository size significantly.
> see mailing-list discussion:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message