[ 
https://issues.apache.org/jira/browse/IVY-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gintas Grigelionis updated IVY-439:
-----------------------------------
    Description: 
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)
{code:xml}
<resolve ...>
    <type-filter types="jar,zip" />
    <organisation-filter orgs="apache" />
    <filter class="com.mycompany.MyCustomFilter" />
</resolve>
{code}

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


> 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)
> {code:xml}
> <resolve ...>
>     <type-filter types="jar,zip" />
>     <organisation-filter orgs="apache" />
>     <filter class="com.mycompany.MyCustomFilter" />
> </resolve>
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to