Return-Path: Delivered-To: apmail-builds-archive@minotaur.apache.org Received: (qmail 59093 invoked from network); 3 Dec 2010 22:25:21 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Dec 2010 22:25:21 -0000 Received: (qmail 74046 invoked by uid 500); 3 Dec 2010 22:25:21 -0000 Delivered-To: apmail-builds-archive@apache.org Received: (qmail 73973 invoked by uid 500); 3 Dec 2010 22:25:21 -0000 Mailing-List: contact builds-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: builds@apache.org Delivered-To: mailing list builds@apache.org Received: (qmail 73965 invoked by uid 99); 3 Dec 2010 22:25:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Dec 2010 22:25:20 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of antoine.toulme@gmail.com designates 209.85.216.50 as permitted sender) Received: from [209.85.216.50] (HELO mail-qw0-f50.google.com) (209.85.216.50) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Dec 2010 22:25:11 +0000 Received: by qwi4 with SMTP id 4so5126392qwi.23 for ; Fri, 03 Dec 2010 14:24:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:content-type :mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=kpsNO1wGHLGTli+ZBGu3eCdSt4HPXqJ9EYBoDLVTPXE=; b=QpOwqJnW1N7yczMW7ePooTDJL3jX/cRT0xlYmJZQTyvf/Gs4hvUMQm4HGUUV6El7H5 FoqUxy2VX33DJ1y0p9r7dfRkM2JnAQOqh1GioIUmoaMhclU7i2tncxA6a5zZvW8FosAh k50BsnLvKnskucR04/CcEpqZoZ5onI9pNxryE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=Z9lHz22pUbBDKXEL3n45ZiSNYuuO4Dq2nNcJy09HUGIJXT+B1BC8yAQDNDhgKu6bRQ tukn5qvsQoLfjCbP1TgMiOfr0yoxvCL28udHkqC+ndtRtMx0DuPryNOgaq5P5CrlDg73 imSI1ZgXRClEPpVJm97queCW8LAY/8Vt+GgpU= Received: by 10.220.94.207 with SMTP id a15mr528482vcn.202.1291415090875; Fri, 03 Dec 2010 14:24:50 -0800 (PST) Received: from [192.168.1.185] ([173.164.162.1]) by mx.google.com with ESMTPS id y14sm433909vch.4.2010.12.03.14.24.49 (version=SSLv3 cipher=RC4-MD5); Fri, 03 Dec 2010 14:24:50 -0800 (PST) Sender: Antoine Toulme Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1081) Subject: Re: Workspace conflicts with hudson From: Antoine Toulme In-Reply-To: Date: Fri, 3 Dec 2010 14:24:48 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <24CB8105-C840-43F9-9995-88E13DD01480@lunar-ocean.com> References: To: builds@apache.org X-Mailer: Apple Mail (2.1081) X-Virus-Checked: Checked by ClamAV on apache.org No, there is an option for Maven jobs to run with their private Maven = repo. I highly recommend it. On Dec 3, 2010, at 11:05 AM, Benson Margulies wrote: > Apache Hudson experts, >=20 > Is the best plan to use locks and latches to make sure that two jobs > don't try to modify a shared maven local repository at the same time?