[
https://jira.codehaus.org/browse/MSHARED-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338050#comment-338050
]
Dominique Jean-Prost commented on MSHARED-161:
----------------------------------------------
Hello,
Any news concerning this issue ? The workaround mentionned in
http://jira.codehaus.org/browse/MWAR-301?focusedCommentId=333877&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-333877
does work though.
By the way, the TODO in java code does seem to agree this point of view ?
{{// TODO new File should be new File(mavenProject.getBasedir(), filterfile )
?}}
Dom
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
