| Key: |
MOJO-951
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Steinar Bang
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
1.
pde-maven-plugin-951.diff (50 kB)
|
|
Environment:
|
maven-2.0.4, jdk 1.5.0_11, linux, Ubuntu 7.10, Intel Pentium M
|
|
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".
|
|
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". |
Show » |
Sort Order:
|
Setting buildDirectory in eclipseBuildScriptProperties does not work (but setting it in buildProperties does)
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/../..