maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olivier Lamy (JIRA)" <>
Subject [jira] Moved: (MSHARED-60) Filtering ${foo.file} evaluates to in full path to pom.xml
Date Sat, 06 Sep 2008 20:41:49 GMT


Olivier Lamy moved MRESOURCES-73 to MSHARED-60:

    Affects Version/s:     (was: 2.2)
        Fix Version/s:     (was: 2.3)
                  Key: MSHARED-60  (was: MRESOURCES-73)
              Project: Maven Shared Components  (was: Maven 2.x Resources Plugin)

> Filtering ${foo.file} evaluates to in full path to pom.xml
> ----------------------------------------------------------
>                 Key: MSHARED-60
>                 URL:
>             Project: Maven Shared Components
>          Issue Type: Bug
>    Affects Versions: maven-filtering-1.0-beta-1
>         Environment: Windows XP, Maven 2.0.2
>            Reporter: Olivier Lamy
>            Assignee: Olivier Lamy
>            Priority: Critical
>             Fix For: maven-filtering-1.0-beta-2
> 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