Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: pde (retired)
-
Labels:None
-
Environment:maven-2.0.4, jdk 1.5.0_11, linux, Ubuntu 7.10, Intel Pentium M
-
Complexity:Intermediate
-
Number of attachments :
Description
This does not work:
<eclipseBuildScriptProperties>
<buildDirectory>${project.build.directory}</buildDirectory>
</eclipseBuildScriptProperties>
(though that's what I expected from the documentation http://mojo.codehaus.org/pde-maven-plugin/attach-mojo.html )
However this works:
<buildProperties>
<buildDirectory>${project.build.directory}</buildDirectory>
</buildProperties>
It sets the buildDirectory twice in the java command line, first to ../.. from the POM directory (with a full path), and then later to POM directory + "/target".
Here is a patch to the current trunk.head that handles the pdeBuildDirectory problem. The fix allows you to set the pdeBuildDirectory as a property for plugin. If the property is not set then it uses the default way (as right now = project.build.directory/../..