DefaultMavenFileFilter.getDefaultFilterWrappers loads filters from the current directory instead of using basedir

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.