Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of
 gcjtmu-turbine-maven-user-846@m.gmane.org designates 80.91.229.3 as permitted
 sender)
To: users@maven.apache.org
From: =?UTF-8?B?SsO2cmc=?= Schaible <Joerg.Schaible@scalaris.com>
Subject: Re: Maven concurrent builds
Date: Wed, 07 Mar 2012 13:52:07 +0100
Organization: Scalaris AG
Lines: 11
Message-ID: <jj7lln$epr$1@dough.gmane.org>
References: <4F57160D.2050104@gmail.com> <jj769m$m6e$1@dough.gmane.org>
 <CAHhx-GJjvbzzUFLAmYUEyUbxZ0xKHhEqfL24pLLZ871Dy5tMSA@mail.gmail.com>
 <4F573F26.1080603@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8Bit
User-Agent: KNode/4.7.4

Guillaume Polet wrote:

> OK, good to know. Somehow, I always assumed that Maven was actually
> handling concurrency safely.
> Too bad that we have to waste extra space to handle this, but at least
> there are easy workarounds.

If you use a repository manager in your intranet, you may simple wipe the 
local repo every time.

- Jörg


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org