[
https://issues.apache.org/jira/browse/IVY-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566552#action_12566552
]
Xavier Hanin commented on IVY-472:
----------------------------------
If you use type to distinguish the debug and release artifacts, you have to use
the [type] token in your pattern in your repository. It doesn't mean you need
to use it when you call retrieve, for instance (assuming you always retrieve
only type, by splitting the types in confs too). Then you can have a path
independent of artifact type which should make VisualStudio happy.
I agree that in this case the configuration is a bit redundant with the type.
But I don't think it's a big deal.
About status and resolver, some make status a first class citizen, and split
statuses among resolvers. Other don't really care about status, and put all
necessary information in the revision. Ivy needs to dapat to very different use
cases, so I think status, resolver and configuration each owe their place in
Ivy.
> 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.
