You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@codehaus.org> on 2014/11/25 21:49:13 UTC

[jira] (MRESOURCES-151) Path for "filters" parameter is relative to the place from where the build was run

     [ https://jira.codehaus.org/browse/MRESOURCES-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MRESOURCES-151.
-------------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> 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 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 was sent by Atlassian JIRA
(v6.1.6#6162)