Path for "filters" parameter is relative to the place from where the build was
run
----------------------------------------------------------------------------------
Key: MRESOURCES-151
URL: https://jira.codehaus.org/browse/MRESOURCES-151
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Components: filtering
Affects Versions: 2.5
Reporter: Julien HENRY
Priority: Minor
I am using copy-resources goal in a multi-module project with the following
configuration in a child module:
{code:xml}
<configuration>
<filters>
<filter>src/main/filters/filter.properties</filter>
</filters>
</configuration>
{code}
The filter path is resolved differently depending on the place from where I run
the build (root aggregator project or child module).
The workaround is to always give absolute path using basedir property:
{code:xml}
<configuration>
<filters>
<filter>${basedir}/src/main/filters/filter.properties</filter>
</filters>
</configuration>
{code}
What is confusing is that the first configuration works fine in the global
filter definition:
{code:xml}
<build>
<filters>
<filter>src/main/filters/filter.properties</filter>
</filters>
</build>
{code}
Could you please make the behavior more consistent or at least put a warning in
documentation of the "filters" parameter.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
