Return-Path: Delivered-To: apmail-maven-issues-archive@locus.apache.org Received: (qmail 90288 invoked from network); 26 Jan 2009 21:02:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Jan 2009 21:02:47 -0000 Received: (qmail 12143 invoked by uid 500); 26 Jan 2009 21:02:47 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 12103 invoked by uid 500); 26 Jan 2009 21:02:47 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 12092 invoked by uid 99); 26 Jan 2009 21:02:47 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jan 2009 13:02:47 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [63.246.2.115] (HELO codehaus01.managed.contegix.com) (63.246.2.115) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jan 2009 21:02:40 +0000 Received: from codehaus01.managed.contegix.com (localhost.localdomain [127.0.0.1]) by codehaus01.managed.contegix.com (Postfix) with ESMTP id B9C6814A8103 for ; Mon, 26 Jan 2009 15:02:19 -0600 (CST) Message-ID: <15986260.1233003739740.JavaMail.haus-jira@codehaus01.managed.contegix.com> Date: Mon, 26 Jan 2009 15:02:19 -0600 (CST) From: "Paul Gier (JIRA)" To: issues@maven.apache.org Subject: [jira] Commented: (MCOMPILER-51) incorrectly evaluates ${project.build.directory} as current-dir relative In-Reply-To: <81630489.1169665947419.JavaMail.haus-jira@codehaus01.managed.contegix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 4e90ceb663894a42f12c0e28abbab431 X-Virus-Checked: Checked by ClamAV on apache.org [ http://jira.codehaus.org/browse/MCOMPILER-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162579#action_162579 ] 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? > 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: > > /Volumes/RamDisk/target > ${project.build.directory}/classes > Incorrectly sends javac output to /Users/matt/myProject/Volumes/RamDisk/target/classes > However: > > /Volumes/RamDisk/target > ${project.build.directory}/classes > 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