Return-Path: 
 <ivy-user-return-2374-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: (qmail 17161 invoked from network); 1 Feb 2008 22:52:58 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 1 Feb 2008 22:52:58 -0000
Received: (qmail 60752 invoked by uid 500); 1 Feb 2008 22:52:49 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 60567 invoked by uid 500); 1 Feb 2008 22:52:49 -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 60558 invoked by uid 99); 1 Feb 2008 22:52:49 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2008 14:52:49 -0800
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 (athena.apache.org: local policy)
Received: from [212.73.163.153] (HELO esmtp.rymdweb.com) (212.73.163.153)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Feb 2008 22:52:20 +0000
Received: from [192.168.1.102] ([89.160.97.30])
	(authenticated bits=0)
	by medusa.rymdweb.com (8.13.8/8.13.8/Debian-2) with ESMTP id m11MqOV2010552
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <ivy-user@ant.apache.org>; Fri, 1 Feb 2008 23:52:24 +0100
Message-ID: <47A3A2B4.5050205@soop.se>
Date: Fri, 01 Feb 2008 23:52:36 +0100
From: Christoffer Soop <lists@soop.se>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: ivy-user@ant.apache.org
Subject: Using the configuration as part of the artifact pattern
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hi!

I am trying to set up a custom repository where artifacts are stored in
a configuration subdirectory of the module. For this I am using the
artifact pattern

   [organisation]/[module]/[revision]/[conf]/[artifact].[ext]

... in the resolver configuration.

However, using this artifact pattern always makes the [conf] part be
replaced by "default", regardles of what configurations are resolved. To
reproduce this behaviour, just call the default target of the
filter-framework project in the configuration example from the ivy
distribution, with the "ivy.local.default.artifact.pattern" pattern set.

   cd src/example/configurations/multi-projects/filter-framework
   ant -D:ivy.local.default.artifact.pattern=\
    [organisation]/[module]/[revision]/[conf]/[artifact].[ext]

Is this behaviour a defect or am I missing something?

If I am missing something, could somebody kindly give me a hint on how
to make the configuration tutorial work an artifact path similar to
mine? Would be much appreciated...

NOTE: When using the [conf] placeholder in the *retrieve* pattern,
[conf] is replaced by the different configurations, exactly as stated in
the configurations tutorial.

Sincerely,

	Chris

PS/I suppose a work around would be to use a homegrown flavour
attribute, i.e. specifying the publicised artifacts as

   <artifact name="module-artifact" type="jar" flavour="Debug" />

... dependencies a

   <dependency org="org" name="module" rev="1.0" flavour="Debug" />

... and using an artifact pattern of

  [organisation]/[module]/[revision]/[flavour]/[artifact].[ext]

... but it would be rather nice to use the configuaration feature, since
different configurations is exactly what I need.