[
https://issues.apache.org/jira/browse/IVY-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488102
]
Xavier Hanin commented on IVY-472:
----------------------------------
The problem is that artifacts can be part of several confs, so during
publication Ivy should look at all places where the artifact can be depending
on the confs in which it is published. The same apply for resolvers. I'm not
sure people would really the implication of using a conf token in such
patterns, so I'm not really in favor of this feature.
Any other opinion?
> 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.
