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 Wed, 06 Feb 2008 20:33:08 GMT


Xavier Hanin commented on IVY-472:

I don't think someone suggest using status for this, but rather a custom attribute. For your
use case (debug vs release artifacts), I think the type could be used (for instance debug-dll
and release-dll). In this case remember to use the ext attribute to have a dll extension in
both cases. 

About the status not being available, first the status is defined by module, not by artifact.
Second the problem is that Ivy doesn't have the status information on the dependency declaration,
thus it would be very difficult to find the dependency if using a status token. 

> 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