Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 16473 invoked from network); 24 Nov 2008 19:25:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Nov 2008 19:25:41 -0000 Received: (qmail 40933 invoked by uid 500); 24 Nov 2008 19:25:50 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 40916 invoked by uid 500); 24 Nov 2008 19:25:50 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 40905 invoked by uid 99); 24 Nov 2008 19:25:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Nov 2008 11:25:50 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jeffrey.fredrick@gmail.com designates 216.239.58.184 as permitted sender) Received: from [216.239.58.184] (HELO gv-out-0910.google.com) (216.239.58.184) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Nov 2008 19:24:23 +0000 Received: by gv-out-0910.google.com with SMTP id n29so398821gve.16 for ; Mon, 24 Nov 2008 11:25:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=2t2S0Ij56arpeNIWU9+gLjXpaaj+pATp5AA/Wqxp2Lc=; b=PgLZLoUUISjoI3GWMV4D9QjuUZvV1Kdgz6CcCAEuWtcj8db8BV7nLvWOrE9yuqfRAt N5/L3tefvaIFWTPS83QYzn0WXwcEzHpsPczTJACN3ZKaSx9NyQR3xbmMfzCIYQ5M3EjV 24499je/5oU0T2ySjaKfU63A1QJ7aGGsGtt0Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=JAlUHGA+zRpJ1FuWqFeOCFogL+b+2d4G657jYC9H0uRmHD/pI4ectxTFLmPpaVKuPy q8rmKRpgGcl4Qdudz6EpiXbAYRaY59OdY0yERkdhgtjYmHXv9rP9Dtibw2q/aGcl/1lV /p/0SxyI9I0sCNEmJ5MwmDWcHHtIRC/d4XCo0= Received: by 10.103.193.12 with SMTP id v12mr1203723mup.23.1227554245701; Mon, 24 Nov 2008 11:17:25 -0800 (PST) Received: by 10.103.119.5 with HTTP; Mon, 24 Nov 2008 11:17:25 -0800 (PST) Message-ID: Date: Mon, 24 Nov 2008 11:17:25 -0800 From: "Jeffrey Fredrick" To: ivy-user@ant.apache.org Subject: Re: Noobie publishing question In-Reply-To: <492ABFEE.8010102@hoovers.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6EDA1C2DBB743143A80D64006C8C0FF2DADC44__3673.80127213455$1226067972$gmane$org@fe-mail29.de.bosch.com> <6EDA1C2DBB743143A80D64006C8C0FF2DADEE2@fe-mail29.de.bosch.com> <333776.51298.qm@web30807.mail.mud.yahoo.com> <4927127C.7030507@hoovers.com> <7916a6a60811211233u7ad89d34gfea65a2fc6c945b6@mail.gmail.com> <49272843.4020109@hoovers.com> <492ABFEE.8010102@hoovers.com> X-Virus-Checked: Checked by ClamAV on apache.org Other people can correct me but I think normally you'd have a single repository but release and development versions of your artifacts. Either way I find it odd to have developers publishing directly to the repository. That seems like something your build server should handle for you. Jtf On Mon, Nov 24, 2008 at 6:53 AM, csanders wrote: > Not sure whats a good approach, ideally we'd have a release repo and a > development repo. > > Jeffrey Fredrick wrote: >> On Fri, Nov 21, 2008 at 1:29 PM, csanders wrote: >> >>> >>> We are a team of about 20 I was hoping to have a publicly shared repo >>> where >>> all team members could publish their artifacts, maybe I'm taking the >>> wrong >>> approach ? >>> >> >> When you assemble a release are you going to use the artifacts in that >> repository or is that just for day-to-day use? -- http://blog.jeffreyfredrick.com