Return-Path: Delivered-To: apmail-archiva-users-archive@www.apache.org Received: (qmail 32468 invoked from network); 9 Oct 2009 10:43:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 9 Oct 2009 10:43:00 -0000 Received: (qmail 44093 invoked by uid 500); 9 Oct 2009 10:43:00 -0000 Delivered-To: apmail-archiva-users-archive@archiva.apache.org Received: (qmail 44027 invoked by uid 500); 9 Oct 2009 10:43:00 -0000 Mailing-List: contact users-help@archiva.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@archiva.apache.org Delivered-To: mailing list users@archiva.apache.org Received: (qmail 44017 invoked by uid 99); 9 Oct 2009 10:43:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Oct 2009 10:43:00 +0000 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 (nike.apache.org: domain of odeaching@gmail.com designates 209.85.222.198 as permitted sender) Received: from [209.85.222.198] (HELO mail-pz0-f198.google.com) (209.85.222.198) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Oct 2009 10:42:50 +0000 Received: by pzk36 with SMTP id 36so4020497pzk.5 for ; Fri, 09 Oct 2009 03:42:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=Koaa+JFHc85UFhwY2Slf2PvwWYW3tbQi8gyir4JnMWM=; b=GQhCLfRkrQ05SS9/b7CT8HAyTW0sdi3PtA4c0f5vl4frTvJaYYkdwRDQc+EaI4cfnx O+GFTxnWskem71xvTjCtv3t7tmEmgTbOIJz9kaahYTp4TUMm6j2HSAng7PDfcM8m/oxW qw8DhJXACxef01tIpnT22vKJIs36cuplbgnXs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=amDNRIlyqQpBFJeaxC0H1GsslV+ea8yvS+7Atw6PH4vGt9MuUE1STZBFB+oaiwMmFE zZrdrhr0QO7FnR9IYcpyLXL7xw70S26e/kjYyy+a/OSWEHvr84Z8uJzHeZTUR0V2jdZr HoK8h6nIIBP4tEuPPOJFzz+PkGtXA1tuPvPuU= MIME-Version: 1.0 Received: by 10.115.101.15 with SMTP id d15mr3426814wam.200.1255084948734; Fri, 09 Oct 2009 03:42:28 -0700 (PDT) In-Reply-To: <1255084683.28517.25.camel@asf> References: <1255084683.28517.25.camel@asf> Date: Fri, 9 Oct 2009 18:42:28 +0800 Message-ID: <8667b1bd0910090342t1ed1d032hee61c6b0cf9676d5@mail.gmail.com> Subject: Re: Using http for deploy From: Deng Ching To: users@archiva.apache.org Content-Type: multipart/alternative; boundary=0016e64dca1488421b04757e3c96 X-Virus-Checked: Checked by ClamAV on apache.org --0016e64dca1488421b04757e3c96 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Fri, Oct 9, 2009 at 6:38 PM, Thorsten Scherler < thorsten.scherler.ext@juntadeandalucia.es> wrote: > Hi all, > > I am looking for information about using http protocol to deploy our > artifacts. > > In our use case Archiva is a proxy for the external repos (like the > official apache one) but we want to deploy our own artifacts on it. > > We found some information about doing it with scp:// but we would like > to use http:// instead. > > Is this possible and if so can somebody point me to some documentation > bout it? > Yes it's possible, here's the documentation for that.. http://archiva.apache.org/docs/1.2.2/userguide/deploy.html You would also need to grant the user the Repository Manager role for the repo in order to be able to deploy to it. > > TIA > > salu2 > > P.S. It took me a while to find > http://archiva.apache.org/mail-lists.html since I did not found a direct > link to page. In the end I need to use a search engine to find it. > Noted, thanks! :) -Deng -- > Thorsten Scherler > Open Source Java > > Sociedad Andaluza para el Desarrollo de la Sociedad > de la Informaci=F3n, S.A.U. (SADESI) > > > > > --0016e64dca1488421b04757e3c96--