[jira] [Closed] (MDEP-214) Accompany outputFilterFile with possibility of of definining used property name.

["Michael Osipov (JIRA)" <ji...@apache.org>]

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

Michael Osipov closed MDEP-214.
-------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still persists, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> Accompany outputFilterFile with possibility of of definining used property name.
> --------------------------------------------------------------------------------
>
>                 Key: MDEP-214
>                 URL: https://issues.apache.org/jira/browse/MDEP-214
>             Project: Maven Dependency Plugin
>          Issue Type: Improvement
>          Components: build-classpath
>    Affects Versions: 2.1
>            Reporter: Tuomas Kiviaho
>            Priority: Minor
>         Attachments: filter_property_name.patch
>
>
> Currently filter format is hardcoded as 'classpath=xxxxx'. assembly plugin bundles files and filter together so each classpath property file (unix/windows/..) requires separate assembly plugin definition for each classpath variant. By exposing an 'outputFilterName' parameter, this extra step would be removed. Instead of above one could have classpath.unix=xxxxx, classpath.windows=yyyyy. One step further would be the possibility of appending these into same file, but only if that wouldn't require yet another parameter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)