[
http://jira.codehaus.org/browse/MOJO-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alin Dreghiciu updated MOJO-951:
--------------------------------
Attachment: pde-maven-plugin-951.diff
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/../..
> Setting buildDirectory in eclipseBuildScriptProperties does not work (but
> setting it in buildProperties does)
> -------------------------------------------------------------------------------------------------------------
>
> Key: MOJO-951
> URL: http://jira.codehaus.org/browse/MOJO-951
> Project: Mojo
> Issue Type: Bug
> Components: pde
> Environment: maven-2.0.4, jdk 1.5.0_11, linux, Ubuntu 7.10, Intel
> Pentium M
> Reporter: Steinar Bang
> Attachments: pde-maven-plugin-951.diff
>
>
> 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".
--
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
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
