[
http://jira.codehaus.org/browse/MOJO-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113273
]
Pawel S. Veselov commented on MOJO-944:
---------------------------------------
the reason for the patch as I saw it, is that normally JAVA_HOME/bin is *not*
in the path. Or the JAVA_HOME/bin that is in the path is different from the
JAVA_HOME that maven is configured to use. So I wanted to make sure that the
right javah is picked up, or there is a way to ensure that it does. And it
should really always be ${java.home}/bin/javah, and *not*
${jre.home}/bin/javah...
> javah is not looked up in ${jdk.home}
> -------------------------------------
>
> Key: MOJO-944
> URL: http://jira.codehaus.org/browse/MOJO-944
> Project: Mojo
> Issue Type: Bug
> Components: native
> Environment: Linux
> Reporter: Pawel S. Veselov
> Attachments: 3.diff, 4.diff,
> org.codehaus.mojo.natives.compiler.CompilerUtilTest.txt
>
>
> When native:javah is executed, the "javah" path is used for the binary. Only
> on MacOS, the ${jdk.home}/bin/javah is used.
> ${java.home} should be used at all times, because:
> a) One doesn't have to add JDK bin directory to current PATH
> b) The JDK directory in the path may not be the same that is used for Maven
> c) the javah binary in the path may not even be JavaH
> The trivial fix is to roll up
> org.codehaus.mojo.natives.javah.JavahMacOSExecutable into
> org.codehaus.mojo.natives.javah.JavahExecutable.
> Anyone knows how to make native pick up the MacOS executable as a workaround ?
> -- Pawel.
--
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
