[MNG-3747] relative build paths are not path-translated when using prefixed expressions (eg. project.build.directory) in plugin configurations

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0-M1
• Fix Version/s: 2.1.0-M1
• Component/s: Inheritance and Interpolation
• Assignee: John Dennis Casey
• Reporter: John Dennis Casey
• Created: 08/Sep/08 19:21
• Updated: 05/Apr/15 23:47
• Resolved: 08/Sep/08 22:32

Description

example:

  <build>
    <directory>bld</directory>
    <plugins>
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <executions>
          <execution>
            <id>test</id>
            <phase>test</phase>
            <goals>
              <goal>run</goal>
            </goals>
            <configuration>
              <tasks>
                <ant dir="${project.build.directory}/test-classes" antfile="${project.build.directory}/test-classes/test.build.xml" />
              </tasks>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

When the antrun plugin executes, the expressions will be resolved with relative paths, not absolute ones (as would be the case if they were run through the pathTranslator).

This is a problem with the interpolation post-processor that handles path translation, because it doesn't have any sensitivity to prefixed expressions. In other words, it'll handle build.directory but not project.build.directory.

Issue Links

• is depended upon by: MECLIPSE-187 problem when outputDirectory and testOutputDirectory are absolute
• is depended upon by: MECLIPSE-269 "Can't canonicalize system path" error using the goal eclispse:eclipse
• is duplicated by: MNG-4083 project.build.directory not set properly for plugins
• relates to: MECLIPSE-99 The plugin seems to append ${basedir} regardless of the nature of ${pom.build.output.directory}.