[MNG-3475] Some directories are not basedir aligned

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.8
• Fix Version/s: 2.1.0-M1
• Component/s: POM
• Flags: Patch
• Assignee: John Dennis Casey
• Reporter: Benjamin Bentmann
• Created: 21/Mar/08 13:15
• Updated: 05/Apr/15 14:54
• Resolved: 25/Jun/08 15:55

Description

The output from

<echo>${project.build.sourceDirectory}</echo>
<echo>${project.build.testSourceDirectory}</echo>
<echo>${project.build.scriptSourceDirectory}</echo>
<echo>${project.build.directory}</echo>
<echo>${project.build.outputDirectory}</echo>
<echo>${project.build.testOutputDirectory}</echo>
<echo>${project.reporting.outputDirectory}</echo>

delivers something like

[echo] M:\maven\z\antrun\src\main\java
[echo] M:\maven\z\antrun\src\test\java
[echo] src/main/scripts
[echo] M:\maven\z\antrun\target
[echo] M:\maven\z\antrun\target\classes
[echo] M:\maven\z\antrun\target\test-classes
[echo] target/site

revealing that neither the script source directory nor the reporting output directory are basedir aligned.

Issue Links

• is depended upon by: MNG-3822 [regression] POM interpolation does not use basedir-aligned build directories
• is related to: MNG-1927 ${project.build.directory} different in M2.0 & M2.0.1
• is related to: MNG-3741 CLONE maven-plugin-tools-api requires relative script root paths
• relates to: MNG-3498 StringIndexOutOfBounds -1 during path translation while reading pom.xml
• relates to: MNG-4061 [regression] expressions not interpolated the same in antrun configuration
• relates to: MNG-3877 Reporting output directory not basedir aligned when queried from MavenProject