ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <>
Subject [jira] Commented: (IVY-472) conf not supported as pattern filtering token
Date Fri, 21 Dec 2007 07:41:43 GMT


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:
<sftp name="remote">
<ivy pattern="sftp://user:password@host:port/repository/[module]/[platform]/[module]-[revision]-[branch].xml"/>
<artifact pattern="sftp://user:password@host:port/repository/[module]/[platform]/[artifact]-[revision]-[branch].[ext]"/>

<artifact name="IvyTest" type="dll" ext="dll" conf="net11" platform="net11" />
<artifact name="IvyTest" type="dll" ext="dll" conf="net20" platform="net20" />

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

View raw message