[
http://jira.codehaus.org/browse/MCOMPILER-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Bishop closed MCOMPILER-51.
--------------------------------
Resolution: Fixed
This now works in Maven 2.0.9.
> <outputDirectory> incorrectly evaluates ${project.build.directory} as
> current-dir relative
> ------------------------------------------------------------------------------------------
>
> Key: MCOMPILER-51
> URL: http://jira.codehaus.org/browse/MCOMPILER-51
> 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 ${project.build.directory} 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>${project.build.directory}/classes</outputDirectory>
> Incorrectly sends javac output to
> /Users/matt/myProject/Volumes/RamDisk/target/classes
> However:
> <build>
> <directory>/Volumes/RamDisk/target</directory>
> <outputDirectory>${project.build.directory}/classes</outputDirectory>
> Correctly sends javac output to /Volumes/RamDisk/target/classes
> As a note, other users of an absolute ${project.build.directory} 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:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
