You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Matt Bishop (JIRA)" <ji...@codehaus.org> on 2007/01/24 20:12:27 UTC
[jira] Created: (MCOMPILER-51) incorrectly
evaluates ${project.build.directory} as current-dir relative
<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
[jira] Commented: (MCOMPILER-51) incorrectly
evaluates ${project.build.directory} as current-dir relative
Posted by "Paul Gier (JIRA)" <ji...@codehaus.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?
> <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
[jira] Commented: (MCOMPILER-51) incorrectly
evaluates ${project.build.directory} as current-dir relative
Posted by "Matt Bishop (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCOMPILER-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85931 ]
Matt Bishop commented on MCOMPILER-51:
--------------------------------------
I meant to say:
<outputDirectory>/Volumes/RamDisk/target/classes</outputDirectory>
Correctly sends...
> <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
[jira] Closed: (MCOMPILER-51) incorrectly
evaluates ${project.build.directory} as current-dir relative
Posted by "Matt Bishop (JIRA)" <ji...@codehaus.org>.
[ 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