[
https://issues.apache.org/jira/browse/IVY-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483097
]
Xavier Hanin commented on IVY-439:
----------------------------------
This is a good idea, and this shouldn't too difficult to implement since the
API already use a Filter, we only have to modify the ant task.
I think the implementation should try to be reusable for other cases, like the
conditional patterns (IVY-324). Indeed I think it could be a nice solution to
have a uniform way of addressing the two.
> Add more filters to the Ant tasks
> ---------------------------------
>
> Key: IVY-439
> URL: https://issues.apache.org/jira/browse/IVY-439
> Project: Ivy
> Issue Type: New Feature
> Components: Ant
> Affects Versions: 1.4.1
> Reporter: Maarten Coene
>
> At the moment, it is only possible to specify 1 filter which filters out the
> artifacts based on their type. This is done with the "type" attribute.
> It would be useful to use more filters here, e.g.:
> - a filter based on the status
> - a filter based on the organization
> - a filter based on the branch
> - a combination of the filters above
> - a custom-made filter
> - ...
> Perhaps we could add a "filter" element, somthing like this (something
> similar like the "selector"-type in Ant)
> <resolve ...>
> <type-filter types="jar,zip" />
> <organisation-filter orgs="apache" />
> <filter class="com.mycompany.MyCustomFilter" />
> </resolve>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
