Hi guysthought I would revisit this issue, as I still believe it is a bug.
On Thu, Sep 25, 2008 at 11:17 PM, Emmanuel Venisse
[EMAIL PROTECTED] wrote:
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
Aren't you using i your build a bogus version of the enforcer plugin.
1.0-alpha-3 has such a bug (MENFORCER-11) which forced to download
dependencies.
Arnaud
On Thu, Sep 25, 2008 at 1:55 AM, Craig [EMAIL PROTECTED] wrote:
Our CI server builds and deploys snapshots to our nexus repository
Brilliant! Thank you so much. That was it. I have yet to try the
latest release of the enforcer plugin, but commenting out the use of
version 1.0-alpha-3 made the problem go away.
Thanks again,
Craig
On Mon, Nov 3, 2008 at 5:21 PM, Arnaud HERITIER [EMAIL PROTECTED] wrote:
Aren't you using i
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
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
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
