[
http://jira.codehaus.org/browse/MNG-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241437#action_241437
]
Brian Levine commented on MNG-3472:
-----------------------------------
Wow. I'm really surprised at the responses here. While it is true that CI
systems could provide tools to clean out Maven local repos, this doesn't do
much for the individual developer who finds that all of a sudden, his dev
machine has run out of disk space. This seems like a perfect example of
something that should be configurable in settings.xml with a default value that
is fairly small. On a personal development machine especially, I see no reason
why you'd want to keep old snapshot artifacts. I will post something to the
mailing list to get this issue re-opened.
> configuration possibilities to limit size of local repository
> -------------------------------------------------------------
>
> Key: MNG-3472
> URL: http://jira.codehaus.org/browse/MNG-3472
> Project: Maven 2 & 3
> 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:
> http://www.nabble.com/limit-size-of-local-repository%2C-limit-number-of-snapshots-td16147475s177.html
--
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
