[
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:[EMAIL
PROTECTED]:port/repository/[module]/[platform]/[module]-[revision]-[branch].xml"/>
<artifact pattern="sftp://user:[EMAIL
PROTECTED]: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.
