Yes, it's a common problem on CI server but on developer workstation too if builds are intensive. About CI server, it is necessary to clean sometimes old snapshots because they are generally not used. Continuum have this features since 1.2, I don't know for other CI servers and if they doesn't exist, a cron job is necessary to do the clean.
Emmanuel On Thu, Sep 25, 2008 at 2:03 PM, Baptiste MATHUS <[EMAIL PROTECTED]> wrote: > Hi Craig, > > Well, no, I don't think the bug you're referring to is related. > Your problem is a quite common one. > > See this bug http://jira.codehaus.org/browse/MNG-233 and the > dependency:purge-local-repository goal of the maven-dependency-plugin. > You will also find interesting relating information here: > http://jira.codehaus.org/browse/CONTINUUM-1693. In fact, though it's a > continuum bug, it's not a problem limited to this continuous integration > server. > > Cheers. > > 2008/9/25 Craig <[EMAIL PROTECTED]> > > > Our CI server builds and deploys snapshots to our nexus repository > > server every time someone commits. > > > > During the build of a snapshot multi-module project, it downloads the > > previous snapshots of the modules to the local repository, even though > > they are in the reactor about to be built. This has the effect of > > causing the local repository to very quickly increase in size, > > containing every snapshot ever built. > > > > I can easily create a cron job to clean these up, but it does seem > > like incorrect behaviour on the part of maven (version 2.0.9). > > > > Will the resolution of this issue > > http://jira.codehaus.org/browse/MNG-3685 (Dependency can't be resolved > > but has been found in the reactor) fix my problem? > > > > thanks. > > Craig > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Baptiste <Batmat> MATHUS - http://batmat.net > Sauvez un arbre, > Mangez un castor ! >
