Return-Path: 
 <ivy-user-return-774-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org
Received: (qmail 99340 invoked from network); 1 May 2007 22:36:40 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 1 May 2007 22:36:40 -0000
Received: (qmail 82508 invoked by uid 500); 1 May 2007 22:36:46 -0000
Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org
Received: (qmail 82488 invoked by uid 500); 1 May 2007 22:36:46 -0000
Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@incubator.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@incubator.apache.org>
List-Post: <mailto:ivy-user@incubator.apache.org>
List-Id: <ivy-user.incubator.apache.org>
Reply-To: ivy-user@incubator.apache.org
Delivered-To: mailing list ivy-user@incubator.apache.org
Received: (qmail 82479 invoked by uid 99); 1 May 2007 22:36:46 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 May 2007 15:36:46 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of xavier.hanin@gmail.com
 designates 64.233.162.230 as permitted sender)
Received: from [64.233.162.230] (HELO nz-out-0506.google.com) (64.233.162.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 May 2007 15:36:39 -0700
Received: by nz-out-0506.google.com with SMTP id j2so2595252nzf
        for <ivy-user@incubator.apache.org>;
 Tue, 01 May 2007 15:36:18 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=a5Eap0ZujOwLVI459ARDc2ZcCix81IM9LwRBXHtGhEAU3nXIWRUn6sPYK4mgYaImGyJ6+XEuqjy/kCeI7MKox1q6SsmityWwZpp9G4QJRsbz7yjlTb2grT9EEuur52GzkeJ/4J7MbuxGFBY1lvVpFOA+/IXvIIrrOOOZ/HxFVyE=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=VgUCKz+U1IfSYVagmFT8E21U5pXYqJE5Rhn48sRYyRUMBQReGFkLmQE7WmEjahG2vr2DAUbliWe8bG63yQPeGZ4Liq+7MAqfF5c94y5GVVcrDt8KXkl1tWIpAclHmNcqoMUQc/V/eYsM0jKtah1bIENxHfa6wOdJ3FXg4zHfbs8=
Received: by 10.114.157.1 with SMTP id f1mr9439wae.1178058977442;
        Tue, 01 May 2007 15:36:17 -0700 (PDT)
Received: by 10.114.171.8 with HTTP; Tue, 1 May 2007 15:36:17 -0700 (PDT)
Message-ID: <635a05060705011536s59fca1f6v2aed8c6b0ab0f61d@mail.gmail.com>
Date: Wed, 2 May 2007 00:36:17 +0200
From: "Xavier Hanin" <xavier.hanin@gmail.com>
To: ivy-user@incubator.apache.org
Subject: Re: what do to with delivered ivy file?
In-Reply-To: <59886BD9013A7D46B98882911FE91B350E1539@ES21SNLNT.srn.sandia.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <59886BD9013A7D46B98882911FE91B350E1539@ES21SNLNT.srn.sandia.gov>
X-Virus-Checked: Checked by ClamAV on apache.org

On 5/2/07, Bagwell, Allen F <afbagwe@sandia.gov> wrote:
>
> I have modules that use ivy:publish.  Here is a code snippet:
>
> <ivy:publish resolver="my-artifacts" pubrevision="${ivy.new.revision}" forcedeliver="true">
>    <artifacts pattern="${cpp.dir.include}/[artifact].[ext]" />
>    <artifacts pattern="${cpp.dir.src}/[artifact].[ext]" />
> </ivy:publish>
>
> My project space looks like:
> build.xml
> include/
> ivy.xml
> src/
>
> The publish call delivers an ivy file at include/ivy.xml with revision and publication info in it.  It always gets generated with forcedeliver="true" because used in tandem with ivy:buildnumber, the revision number otherwise wouldn't increment properly.
>
> My question: is there a way to force the generated ivy file to a different location other than the first directory in the list of artifact patterns?  Perhaps either in newly created dir like ivyrev/ or in the base directory as ivy-[revision].xml so it won't overwrite the real ivy.xml file which is under version control?
I think srcivypattern is what you're looking for:
http://incubator.apache.org/ivy/doc/use/publish.html

Xavier
>
> Thanks,
> Allen
>


-- 
Learn Ivy at ApacheCon: http://www.eu.apachecon.com/
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/