Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
maven-filtering-1.0-beta-1
-
None
-
None
-
Windows XP, Maven 2.0.2
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.
Attachments
Issue Links
- is depended upon by
-
MRESOURCES-20 Filtering ${foo.file} evaluates to in full path to pom.xml
- Closed
-
MWAR-133 Filtering issue: wrong replacement of properties by values from MavenProject object
- Closed
- is duplicated by
-
MSHARED-63 Filtering Resources does not match patterns strictly
- Closed
-
MRESOURCES-56 use (and release) the maven-filtering component
- Closed
- relates to
-
MWAR-133 Filtering issue: wrong replacement of properties by values from MavenProject object
- Closed