[jira] Commented: (MRESOURCES-20) Filtering ${foo.file} evaluates to in full path to pom.xml

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] Commented: (MRESOURCES-20) Filtering ${foo.file} evaluates to in full path to pom.xml

JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/MRESOURCES-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125529 ]

Olivier Lamy commented on MRESOURCES-20:

The issue I see with this patch is the backward comp
The following content :
is currently interpolated to :
With the patch :

> Filtering ${foo.file} evaluates to in full path to pom.xml
> ----------------------------------------------------------
>                 Key: MRESOURCES-20
>                 URL: http://jira.codehaus.org/browse/MRESOURCES-20
>             Project: Maven 2.x Resources Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>         Environment: Windows XP, Maven 2.0.2
>            Reporter: Martin Onis
>            Priority: Minor
>         Attachments: MRESOURCES-20.patch
> If an unresolved variable is encountered, the plugin simply does not replace the variable in the target file.
> If this unresolved variable however ends in ".file}" it will evaluate to a file object that targets the current pom. This results in the replacement being the complete path to that pom (in the 2.1 version of the plugin this results in a ClassCastException).
> The workaround is, of course, not to filter the affected files.
> Though this will not work if other variables in the affected files do need to be replaced.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira