maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephane Nicoll (JIRA)" <>
Subject [jira] Commented: (MRESOURCES-20) Filtering ${foo.file} evaluates to in full path to pom.xml
Date Fri, 05 Sep 2008 16:13:49 GMT


Stephane Nicoll commented on MRESOURCES-20:

see the linked issue. it is already fixed, we need to integrate the new maven filtering shared

> Filtering ${foo.file} evaluates to in full path to pom.xml
> ----------------------------------------------------------
>                 Key: MRESOURCES-20
>                 URL:
>             Project: Maven 2.x Resources Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>         Environment: Windows XP, Maven 2.0.2
>            Reporter: Martin Onis
>            Assignee: Olivier Lamy
>            Priority: Critical
>             Fix For: 2.3
>         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:
For more information on JIRA, see:


View raw message