Return-Path: 
 <notifications-return-297-apmail-ant-notifications-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-notifications-archive@locus.apache.org
Received: (qmail 16590 invoked from network); 21 Dec 2007 07:42:11 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 21 Dec 2007 07:42:11 -0000
Received: (qmail 25173 invoked by uid 500); 21 Dec 2007 07:42:01 -0000
Delivered-To: apmail-ant-notifications-archive@ant.apache.org
Received: (qmail 25147 invoked by uid 500); 21 Dec 2007 07:42:01 -0000
Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:notifications-help@ant.apache.org>
List-Unsubscribe: <mailto:notifications-unsubscribe@ant.apache.org>
List-Post: <mailto:notifications@ant.apache.org>
List-Id: <notifications.ant.apache.org>
Reply-To: dev@ant.apache.org
Delivered-To: mailing list notifications@ant.apache.org
Received: (qmail 25137 invoked by uid 99); 21 Dec 2007 07:42:01 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Dec 2007 23:42:01 -0800
X-ASF-Spam-Status: No, hits=-99.8 required=10.0
	tests=ALL_TRUSTED,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Dec 2007 07:41:39 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 1492B714236
	for <notifications@ant.apache.org>; Thu, 20 Dec 2007 23:41:43 -0800 (PST)
Message-ID: <14332538.1198222903068.JavaMail.jira@brutus>
Date: Thu, 20 Dec 2007 23:41:43 -0800 (PST)
From: "Xavier Hanin (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Commented: (IVY-472) conf not supported as pattern filtering
 token
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/IVY-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553891 ] 

Xavier Hanin commented on IVY-472:
----------------------------------

Ok, I see your point, but the configuration cardinality is a real problem to do this kind of thing as you want in a generic way. As a workaround I suggest to use an extra attribute for your artifacts. For instance:
{code}
<resolvers>
<sftp name="remote">
<ivy pattern="sftp://user:password@host:port/repository/[module]/[platform]/[module]-[revision]-[branch].xml"/>
<artifact pattern="sftp://user:password@host:port/repository/[module]/[platform]/[artifact]-[revision]-[branch].[ext]"/>
</sftp>
</resolvers>
{code} 

{code}
<publications>
<artifact name="IvyTest" type="dll" ext="dll" conf="net11" platform="net11" />
<artifact name="IvyTest" type="dll" ext="dll" conf="net20" platform="net20" />
</publications>
{code} 

I agree there is a redundancy between the configurations and the platform, but you can imagine others configurations too (not platform related).

> conf not supported as pattern filtering token
> ---------------------------------------------
>
>                 Key: IVY-472
>                 URL: https://issues.apache.org/jira/browse/IVY-472
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: unspecified
>         Environment: WinXP x86 with Ant1.7
>            Reporter: Todd Lee
>            Priority: Minor
>
> it seems that [conf] is not currently supported for use as an artifact pattern in an ivy:publish task or as a pattern token for use in resolvers (as raised in ivy-user list here: http://www.nabble.com/publishing-configurations-tf3555931.html). With configurations being such a key component of ivy, it would be nice if the [conf] pattern were better supported across different filtering processes. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.