[ http://jira.codehaus.org/browse/MRESOURCES-20?page=comments#action_68322
]
Eric Bottard commented on MRESOURCES-20:
----------------------------------------
I would suggest raising the priority of this bug as it can have very nasty side
effects, for example when using velocity templates.
It would also be nice to have the possibility to
1- Use other delimiters for properties (ie not only @@ or ${})
2- De-activate the ${} delimiters
> 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
> Type: Bug
> Versions: 2.2
> Environment: Windows XP, Maven 2.0.2
> Reporter: Martin Onis
> Priority: Minor
>
>
> 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
