Return-Path: 
 <ivy-user-return-5254-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 17042 invoked from network); 11 May 2009 21:16:22 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 11 May 2009 21:16:22 -0000
Received: (qmail 52727 invoked by uid 500); 11 May 2009 21:16:21 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 52694 invoked by uid 500); 11 May 2009 21:16:21 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Received: (qmail 52684 invoked by uid 99); 11 May 2009 21:16:19 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 May 2009 21:16:19 +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 (athena.apache.org: domain of needsmoresnow@gmail.com
 designates 209.85.219.217 as permitted sender)
Received: from [209.85.219.217] (HELO mail-ew0-f217.google.com)
 (209.85.219.217)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 May 2009 21:16:11 +0000
Received: by ewy17 with SMTP id 17so3904000ewy.28
        for <ivy-user@ant.apache.org>; Mon, 11 May 2009 14:15:49 -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=ILQ74c24HCyBibkomvyVluTr/HTBE619PDiGX/vv26w=;
        b=rhc5O6zi7InFPuRdTsoOZkBLxcLwoIL9o6OU1FPWBxPBzpl90576ZHlT9HWR9MOga+
         TT2jaClE6CFL9DcmTSVaNIYctd1DxGDifNAdkwFZUkIS9DsAwJsYDAZjr5cLptO5wrRk
         H/c66kvO5mFJ/s32WXTHkXeUCjx+Es+gD8gYY=
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=Ewn5WAn4wEb7Ow+18QtF12gILxki5pwv7MfEuflPk2fvLpoT6CWgbhhAgILWy9ArNn
         O1x2rgVgZ9CJULwrxeWEmwpWy2N0fKnWNSr/HnSoM3IxkdJTGRNWiF9IG5gwbIsYEQMs
         Rw9SKb+rlzBmgv0sG+Vci24T/UUoJVOKuHDjE=
MIME-Version: 1.0
Received: by 10.216.12.67 with SMTP id 45mr3614142wey.218.1242076549158; Mon,
	11 May 2009 14:15:49 -0700 (PDT)
In-Reply-To: <d7681c140905081857h2bf1bbd5k5b0f0f4b54dbfd04@mail.gmail.com>
References: <95f217a60905081639i6f712a92pdc66b241de29f458@mail.gmail.com>
	 <d7681c140905081857h2bf1bbd5k5b0f0f4b54dbfd04@mail.gmail.com>
Date: Mon, 11 May 2009 14:15:49 -0700
Message-ID: <95f217a60905111415r20c72218y831b7603695e413b@mail.gmail.com>
Subject: Re: Location of configuration files as artifacts
From: snowflake <needsmoresnow@gmail.com>
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=0016364d1d557f17bb0469a97b1a
X-Virus-Checked: Checked by ClamAV on apache.org

--0016364d1d557f17bb0469a97b1a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Thanks. I decided to use different types to distinguish the different
artifacts for different confs/views and alter my artifact pattern in the
publish tag to pick them up.  I no longer need to copy the manually to the
build directory.  Please have a look at the configuration below as a few
problems still exist.

ivy.xml:

    <publications>

        <artifact name="ivyplay" type="config"         conf="default"
ext="conf" />
        <artifact name="ivyplay"  type="configDeploy"   conf="deploy"
ext="conf"/>
        <artifact name="ivyplay"    type="configTest"     conf="test"
ext="conf"/>

        <artifact name="ivyplay" type="jar" ext="jar" />
    </publications>

build.xml:

<ivy:publish resolver="myrepository" pubrevision="${revision}"
status="release">

            <artifacts pattern="${conf.dir}/[artifact].[ext]"  />
            <artifacts pattern="${conf.dir.test}/[artifact].[ext]"  />
            <artifacts pattern="${conf.dir.deploy}/[artifact].[ext]"  />

            <artifacts pattern="${build.dir}/[artifact].[ext]" />

</ivy:publish>

my resolver pattern which partitions the artifacts by their types and allows
me to keep track of different module revisions in different folders:

<artifact
pattern="${dest.repo.dir}/no-namespace/[organisation]/[module]/[module]-[revision]/[type]s/[artifact].[ext]"
/>


a couple problems still remain:

1.) if I have files with the same name under the different configurations
and types (i.e. ivyplay.conf both in conf.dir and conf.dir.test), then the
first resolved file (from conf.dir) is used for all successive
dependencies.  In this case all three folders (conf.dir, conf.dir.test, and
conf.dir.deploy) will contain the ivyplay.conf file of (conf.dir).

2.) perhaps this should go in another thread, but:   Is it possible to have
different patterns for different artifacts.  For example, as Joshua
suggested, I can remove the revision from my pattern, but this results in
the revision being removed from all types of artifacts (including my jar
files).  I wish to keep the revision for jars, BUT remove it from
configuration files (as manual work will be required during deployment to
strip them in order for programs to function properly).  I tried a few
things with chained resolvers without any results.  I tried setting up two
resolvers, each with it's own pattern, but I'm not able to have two
different publish tasks (one for jars, and one for artifacts) each of which
would use a different resolver.

Any suggestions are very appreciated.  Thank you all in advance for your
support.

-Sam

--0016364d1d557f17bb0469a97b1a--