[MSHARED-60] Filtering ${foo.file} evaluates to in full path to pom.xml

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: maven-filtering-1.0-beta-1
• Fix Version/s: maven-filtering-1.0-beta-2
• Environment: Windows XP, Maven 2.0.2
• Assignee: Olivier Lamy
• Reporter: Olivier Lamy
• Created: 06/Sep/08 15:40
• Updated: 06/Apr/15 01:49
• Resolved: 06/Sep/08 16:34

Description

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.

Issue Links

• is depended upon by: MRESOURCES-20 Filtering ${foo.file} evaluates to in full path to pom.xml
• is depended upon by: MWAR-133 Filtering issue: wrong replacement of properties by values from MavenProject object
• is duplicated by: MSHARED-63 Filtering Resources does not match patterns strictly
• is duplicated by: MRESOURCES-56 use (and release) the maven-filtering component
• relates to: MWAR-133 Filtering issue: wrong replacement of properties by values from MavenProject object