Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <20622705.1198063483030.JavaMail.jira@brutus>
Date: Wed, 19 Dec 2007 03:24:43 -0800 (PST)
From: "Yuri Khomich (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


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

Yuri Khomich commented on IVY-472:
----------------------------------

As for me, I would love to have [conf] pattern supported in resolvers since it can save a lot of time when defining artifacts.

> 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.