Return-Path: Delivered-To: apmail-archiva-users-archive@www.apache.org Received: (qmail 67754 invoked from network); 11 Aug 2009 20:23:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Aug 2009 20:23:45 -0000 Received: (qmail 10599 invoked by uid 500); 11 Aug 2009 20:23:51 -0000 Delivered-To: apmail-archiva-users-archive@archiva.apache.org Received: (qmail 10478 invoked by uid 500); 11 Aug 2009 20:23:51 -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 10231 invoked by uid 99); 11 Aug 2009 20:23:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Aug 2009 20:23:50 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Aug 2009 20:23:40 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1MaxsM-0001l0-V5 for users@archiva.apache.org; Tue, 11 Aug 2009 13:23:18 -0700 Message-ID: <24925074.post@talk.nabble.com> Date: Tue, 11 Aug 2009 13:23:18 -0700 (PDT) From: Gregory Boissinot To: users@archiva.apache.org Subject: RE: using archiva as ivy repository In-Reply-To: <24920555.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: gregory.boissinot@gmail.com References: <18574568.post@talk.nabble.com> <4AA99A4ABD271B4D86710B80538CE20D02176BF5@INTMAIL01.es.int.atosorigin.com> <24920555.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org I finally found my problem by using the Ant Ivy task ( http://ant.apache.org/ivy/history/latest-milestone/use/makepom.html). This task generates a Maven 2 pom.xml, so I can publish (with ) the target artifact and the pom.xml into Archiva. That's work fine. -- View this message in context: http://www.nabble.com/using-archiva-as-ivy-repository-tp15161852p24925074.html Sent from the archiva-users mailing list archive at Nabble.com.