[
https://jira.codehaus.org/browse/MSHARED-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MSHARED-161.
----------------------------------
Resolution: Fixed
Fix Version/s: maven-filtering-1.2
Assignee: Robert Scholte
Fixed in [r1566347|http://svn.apache.org/r1566347]
> DefaultMavenFileFilter.getDefaultFilterWrappers loads filters from the
> current directory instead of using basedir
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MSHARED-161
> URL: https://jira.codehaus.org/browse/MSHARED-161
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-filtering
> Affects Versions: maven-filtering-1.0-beta-3, maven-filtering-1.0-beta-4
> Reporter: Jeff MAURY
> Assignee: Robert Scholte
> Fix For: maven-filtering-1.2
>
>
> If a POM is a sub module and has filtered configured other than with the
> build section (through the configuration part of the WAR plugin for example),
> then the call to this method will fail if Maven is run from the parent POM
> because the filters are loaded without any regard to absolute/relative paths
> and projet basedir.
> Please note that the Maven project is available to these methods but not used
> for this purpose.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
