Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 39770 invoked from network); 3 May 2008 02:09:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 May 2008 02:09:28 -0000 Received: (qmail 85814 invoked by uid 500); 3 May 2008 02:09:30 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 85797 invoked by uid 500); 3 May 2008 02:09:30 -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 85786 invoked by uid 99); 3 May 2008 02:09:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 May 2008 19:09:30 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [64.202.189.56] (HELO k2smtpout05-01.prod.mesa1.secureserver.net) (64.202.189.56) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 03 May 2008 02:08:35 +0000 Received: (qmail 15829 invoked from network); 3 May 2008 02:08:53 -0000 Received: from unknown (HELO ip-72-167-33-213.ip.secureserver.net) (72.167.33.213) by k2smtpout05-01.prod.mesa1.secureserver.net (64.202.189.56) with ESMTP; 03 May 2008 02:08:53 -0000 Received: from localhost (unknown [127.0.0.1]) by ip-72-167-33-213.ip.secureserver.net (Postfix) with ESMTP id 7904F100BFE for ; Sat, 3 May 2008 02:08:53 +0000 (UTC) Received: from ip-72-167-33-213.ip.secureserver.net ([127.0.0.1]) by localhost (ip-72-167-33-213.ip.secureserver.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hSv4ubfFp0C8 for ; Fri, 2 May 2008 22:08:47 -0400 (EDT) Received: from fawkes.hq.digizenstudio.com (ip70-187-196-88.dc.dc.cox.net [70.187.196.88]) by ip-72-167-33-213.ip.secureserver.net (Postfix) with ESMTP id B5552100A77 for ; Fri, 2 May 2008 22:08:47 -0400 (EDT) Received: by fawkes.hq.digizenstudio.com (Postfix, from userid 1000) id 79FAD9AD2C; Fri, 2 May 2008 22:08:42 -0400 (EDT) Date: Fri, 2 May 2008 22:08:42 -0400 From: Jing Xue To: ivy-user@ant.apache.org Subject: Re: How to use Ivy to publish artifacts to archiva or arifactory? Message-ID: <20080503020842.GA9043@fawkes> Mail-Followup-To: ivy-user@ant.apache.org References: <20080502170546.fkc5q4x28kcook44@intranet.digizenstudio.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-Virus-Checked: Checked by ClamAV on apache.org On Sat, May 03, 2008 at 12:31:49AM +0200, Lasse Knudsen wrote: > > At least with archiva, you could deploy it also (other than webdav) with >> ssh or scp. It'll get picked up by the server during the next scan. See: >> http://archiva.apache.org/docs/1.0.2/userguide/deploy.html > > Yes, I already tried that and I got now an annoying error :-): > > invalid server's version string > > I tried it with: > > > pattern="sftp://Deployer:deployer1@localhost:8081/archiva/repository/internal/[organisation]/[module]/[revision]/ivy.xml" > /> > pattern="sftp://Deployer:deployer1@localhost:8081/archiva/repository/internal/[organisation]/[module]/[revision]/[artifact].[ext]" Is this where your repository actually is in the _underlying_ file system? You'll want to use the actual path to sftp or scp, not the url archiva exposes. -- Jing > > > /> > > > I also tried that with vfs(with ssh, ftp and filie) but I still don't get it running. > > Regards, > Lasse >