ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christoffer Soop (JIRA)" <>
Subject [jira] Commented: (IVY-472) conf not supported as pattern filtering token
Date Thu, 07 Feb 2008 10:55:17 GMT


Christoffer Soop commented on IVY-472:

Ok but if I use type to differentiate between Debug and Release versions of the same DLL,
the type would have to be expressed in either a/ the artifact name or b/ the artifact file
location.  In either case this does not work for me since I need to have the same name and
location for making Visual Studio understand which DLL the solution references. Using different
names would entail changing the Visual Studio reference settings each time I switch between
Debug and Release configuartions and back again, which is unfeasable.

That the status is on a module basis is a feature not a drawback, in my mind. I would like
to be able to do an Integration or Production release of the whole ivy project. True, which
artifacts are included could vary and this brings us back to the whole issue with releasing
a particular configuration.

To me it feels like there is a certain level of redundancy in the concepts of *status*, *configuration*
and also *resolver* since you specify which resolver to use when publishing.  Should the resolver
not follow from the status, assuming you are supposed to use different repositories for different
statuses? Or if the same resolver can be used for different statuses, we ought to be able
to differentiate the artifacts by status in the repository (in my case this needs to be done
by location inside the repository and not by artifact name).

> 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