org = build.getOutputDirectory();
                val = interpolate(org);
                if (org != val) {
                    build.setOutputDirectory(val);
                }
                // TestOutputDirectory
                org = build.getTestOutputDirectory();
                val = interpolate(org);
                if (org != val) {
                    build.setTestOutputDirectory(val);
                }

        // code below...
        translatedPrefixes.add("build.directory");
        translatedPrefixes.add("build.outputDirectory");
        translatedPrefixes.add("build.testOutputDirectory");
        translatedPrefixes.add("build.sourceDirectory");
        translatedPrefixes.add("build.testSourceDirectory");
        translatedPrefixes.add("build.scriptSourceDirectory");

     * where resource {@code targetPath} elements were always interpreted as relative to the output directory
     * ({@code project.build.outputDirectory} or {@code project.build.testOutputDirectory}),
     * not the project base directory. Maven 3 plugins (like maven-resources-plugin) expect to receive
     * the relative path and perform the resolution themselves.
     * </p>
     * <p>

     * are resolved relative to the appropriate output directory ({@code project.build.outputDirectory}
     * or {@code project.build.testOutputDirectory}), <strong>not</strong> the project base directory.
     * </p>
     * <p>
     * In Maven 3, when a resource configuration specifies:
     * </p>
     * <pre>{@code
     * <resource>