Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 7801 invoked from network); 10 Aug 2009 21:45:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Aug 2009 21:45:54 -0000 Received: (qmail 47838 invoked by uid 500); 10 Aug 2009 21:46:01 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 47760 invoked by uid 500); 10 Aug 2009 21:46:01 -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 47750 invoked by uid 99); 10 Aug 2009 21:46:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Aug 2009 21:46:01 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of g.clitheroe@gmail.com designates 209.85.222.181 as permitted sender) Received: from [209.85.222.181] (HELO mail-pz0-f181.google.com) (209.85.222.181) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Aug 2009 21:45:51 +0000 Received: by pzk11 with SMTP id 11so6971889pzk.10 for ; Mon, 10 Aug 2009 14:45:30 -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 :content-transfer-encoding; bh=rHmWSjj+5o93tCIcpqqt1xkPAOyKFza8FIMwaD4ysSw=; b=gRTFaywjqw/DmeVORv+MoPn53FPCmv0s6BVIVcd9F70cXFoXT+ApgmmcLgbVrG76yv onuSN04cuI3X33n1ioTrnUsVU6SuFzCNIH+1+j3EBbJe7KbyGRci1Pm0oAQQpK1z8sYr 3NmR+RMoqARhi0xAnkvhI05tft9kPjzB8hkyk= 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:content-transfer-encoding; b=Uuf2LI+1Fk/vbpAGgVuRPbXLAnl/txwFwX/XchqM13CGjXd6TdEmOUnRp+VW3jDFI1 osl9FAciMaJRRzFKyOV5oD9uldp2H5vkANfuXWDDl16GTstaVimSM4RWNZpuivi8qoE1 8n+ueOX8jtyNu3CAxy3UHYWoJEIHJf91VXTXg= MIME-Version: 1.0 Received: by 10.115.59.2 with SMTP id m2mr299554wak.214.1249940730013; Mon, 10 Aug 2009 14:45:30 -0700 (PDT) In-Reply-To: References: Date: Tue, 11 Aug 2009 09:45:29 +1200 Message-ID: <14479a010908101445i42aea996x4b138ed2af271c16@mail.gmail.com> Subject: Re: Help with resolver pattern for publishing From: Geoff Clitheroe To: ivy-user@ant.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi Topher, some fragments from our ivy-settings and an ivy file below. The pattern in the resolver takes it's values from the settings in the ivy.xml files so in this case we publish a war, and sources and javadoc jars. Cheers, Geoff Ivy settings: ... property name=3D"ivy.shared.m2.ivy.pattern" value=3D"[organisation]/[module]/[revision]/[artifact]-[revision](-[class= ifier]).[ext]" override=3D"false"/> ... ... ... ivy.xml .... .... On Tue, Aug 11, 2009 at 9:30 AM, Chris Marks wrote: > Hi all, > I've been using Ivy for dependency resolution for a couple months now and= I > love it. =A0Now I have a project (called data-collector) that I want to > publish to a private repository to be consumed by other Ivy and Maven > projects. =A0My problem is that I want to publish the jar, sources and ja= vadoc > files to the repository using the ibiblio naming conventions, but can't m= ake > Ivy publish it the way I want. =A0Here's what I've been able to do so far= : > I've been able to use to successfully generate a pom. =A0My > first publish attempts were successful to the repository (Artifactory) an= d > it published with the names data-collector-1.0-SNAPSHOT.jar and > data-collector-1.0-SNAPSHOT.pom. =A0I used a url resolver with the artifa= ct > pattern of " > http://myserver/publishRepo/[organization]/[module]/[revision]/[artifact]= -[revision].[ext]". > and publish artifact pattern of "${dist.packageDir}/[artifact].[ext]". > I then created the source jar on my machine as data-collector-sources.jar > and tried to publish, to no avail. =A0I changed where the jar, pom and so= urces > files were created to a structure that lead to the publish artifact patte= rn > of "${dist.packageDir}/[type]/[artifact].[ext]" and a resolver pattern of > http://myserver/publishRepo/[organization]/[module]/[revision]/[artifact]= -[revision]-[type].[ext]. > This published, but gave me data-collector-1.0-SNAPSHOT-jar.jar, which Iv= yDE > and other tools would not resolve out of the box. =A0I want to keep the > resolution of my artifacts as close to "out-of-the-box" as possible. > So, how can I configure Ivy and my Ant build script to publish my files a= s > data-collector-[revision].jar, data-collector-[revision].pom, > data-collector-[revision]-sources.jar, and > data-collector-[revision]-javadoc.jar? > > Thanks, > topher >