[
http://jira.codehaus.org/browse/MRESOURCES-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy reopened MRESOURCES-20:
------------------------------------
The issue was marked fixed only because maven-filtering component fixes the
ClassCastException.
But if you have a property
{code}
fileValue=${foo.file}
{code}
If this is not found in properties files, project.build.filters,
project.properties and mavenSession.executionProperties, you will have
${foo.file} interpolated with the pom full path.
> 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
> 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, ReflectionProperties.java
>
>
> 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
