[
http://jira.codehaus.org/browse/MSHARED-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251090#action_251090
]
Dennis Lundberg commented on MSHARED-161:
-----------------------------------------
Can you supply a sample project that shows the problem?
> DefaultMavenFileFilter.getDefaultFilterWrappers loads filters from the
> current directory instead of using basedir
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MSHARED-161
> URL: http://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,
> maven-filtering-1.0
> 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 contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
