Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 8521 invoked from network); 21 Nov 2008 23:11:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Nov 2008 23:11:29 -0000 Received: (qmail 63554 invoked by uid 500); 21 Nov 2008 23:11:37 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 63530 invoked by uid 500); 21 Nov 2008 23:11:37 -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 63519 invoked by uid 99); 21 Nov 2008 23:11:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Nov 2008 15:11:37 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mgitman@gmail.com designates 209.85.128.185 as permitted sender) Received: from [209.85.128.185] (HELO fk-out-0910.google.com) (209.85.128.185) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Nov 2008 23:10:14 +0000 Received: by fk-out-0910.google.com with SMTP id 19so1222584fkr.12 for ; Fri, 21 Nov 2008 15:10:48 -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:references; bh=89/6t6ndeL7qUKs/vov0ctXt0uHIjp+hPfrj+aMLo3E=; b=SAhMkSDtPkgH6qVy/qZZ2maLJ6EfLqyxzRdsZnowD79XanlRzEaeTArxqAypgWLPa7 qWgji3vqG8sZqVG7cRpts1fSl5cfnIKw/CF0GFCxcyWPtkDA8Oc98+W3cRzi+gXGZjap 0onjf6MV1h0a0F8/2GznVPd4TBHCDprJrOxwo= 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:references; b=WN2v4mR6hVubbvrDI7SZ0M0Yds/QXbYw9GXWPZyFNijJZVdYXyjE9rYYruSlD2yB2r ZxeAZFvx4h8QYo21Uzm/xOs93x82z/OJl+2CMkPyhaqwHdEoTz/VFJV5JIIvMLaysbeF GNsQTpJnouZGF4GoA01L1iYLcHnU9lw0WP6rE= Received: by 10.187.227.5 with SMTP id e5mr186430far.86.1227309048883; Fri, 21 Nov 2008 15:10:48 -0800 (PST) Received: by 10.187.197.11 with HTTP; Fri, 21 Nov 2008 15:10:48 -0800 (PST) Message-ID: <7916a6a60811211510u808d920wd8488825605a1f12@mail.gmail.com> Date: Fri, 21 Nov 2008 15:10:48 -0800 From: "Mitch Gitman" To: ivy-user@ant.apache.org Subject: Re: Noobie publishing question In-Reply-To: <49272843.4020109@hoovers.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_124614_25983042.1227309048873" 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> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_124614_25983042.1227309048873 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline No, not at all. Kirby's approach of using SFTP (or FTP) is fine. As for filesystem access, here's one possible ecosystem where a filesystem resolver would work fine: - The Ivy repository is on a Linux box. The permissions are to allow anonymous browsing but prevent anonymous uploads. - The developers and the CI system are on Windows boxes. In order to do ivy:publish, the developers and CI system have Samba accounts set up to allow authenticated access to the Ivy repository server. 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 ? ------=_Part_124614_25983042.1227309048873--