All, It appears that the behavior I described in my previous email regarding snapshot behavior in the local repository is expected Maven behavior. I found the following issue that was raised some time ago regarding this:
http://jira.codehaus.org/browse/MNG-3472 This issue was closed as "won't fix" and I'd like to request that it be re-opened. The general reason behind closing this was that that CI tools should be responsible for cleaning up the local repository periodically thereby removing the old versions of snapshot artifacts. While I completely disagree with this, I also think it misses the point. Individual developers will suffer from this problem as well on their personal dev machines. Is it each developer's responsibility to understand the details of how snapshot artifacts are managed in the local repository and periodically clean up after Maven? I don't think so. It seems like the best solution here is to allow a retention policy to be defined in the settings.xml including a default value which is fairly small. I'm not sure there's even a use-case for individual developers wanting to maintain multiple old versions of snapshot artifacts in their local repos. Please re-open this issue. Thanks. -brian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
