[
https://issues.apache.org/jira/browse/IVY-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553430
]
Yuri Khomich commented on IVY-472:
----------------------------------
Imagine that we have an application that is used in two environments. Each
environment requires the same libraries that differ in versions. Currently we
have to define dependencies like this:
<dependency org="org" name="lib" rev="1.1.0" conf="distr-env1"/>
<dependency org="org" name="lib" rev="1.1.1" conf="distr-env2"/>
If [conf] pattern was supported in resolver, it would be enough to have single
dependency and put libraries in two separate folders using the following
structure:
+org
+lib
+distr-env1
+distr-env2
> 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.
