maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Gier (JIRA)" <>
Subject [jira] Commented: (MCOMPILER-51) <outputDirectory> incorrectly evaluates ${} as current-dir relative
Date Mon, 26 Jan 2009 21:02:19 GMT


Paul Gier commented on MCOMPILER-51:

This seems to be fixed in Maven 2.0.9.  Although I can't find a specific issue that refers
to this.
Can you test this with Maven 2.0.9 and verify that it is now resolved?

> <outputDirectory> incorrectly evaluates ${} as current-dir
> ------------------------------------------------------------------------------------------
>                 Key: MCOMPILER-51
>                 URL:
>             Project: Maven 2.x Compiler Plugin
>          Issue Type: Bug
>         Environment: Mac OS X 10.4.8, JDK 1.5.0_06
>            Reporter: Matt Bishop
>            Priority: Minor
> This affects 2.0.4, I have not tested on other versions.
> If a pom.xml's ${} is set to an absolute path and the same pom.xml's
project/build/outputDirectory references this property, the compiler sends built classes to
a path relative to the current dir.  However, if the outputDirectory property is hard-coded
to the absolute path, then the build classes are properly dropped in the absolute path.  Example:
> <build>
>   <directory>/Volumes/RamDisk/target</directory>
>   <outputDirectory>${}/classes</outputDirectory>
> Incorrectly sends javac output to /Users/matt/myProject/Volumes/RamDisk/target/classes
> However:
> <build>
>   <directory>/Volumes/RamDisk/target</directory>
>   <outputDirectory>${}/classes</outputDirectory>
> Correctly sends javac output to /Volumes/RamDisk/target/classes
> As a note, other users of an absolute ${} handle the path correctly,
such as the maven-war-plugin.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message