[
https://issues.apache.org/jira/browse/HADOOP-8737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443405#comment-13443405
]
Colin Patrick McCabe commented on HADOOP-8737:
----------------------------------------------
Hi Steve,
Maven requires a JDK to build source code, not simply a JRE:
http://stackoverflow.com/questions/2222560/build-failed-question-maven-jre-or-jdk-problem
The issue is that the JRE does not contain {{javac}}, and without that, you
can't do very much with Maven or ant.
However-- Maven can be configured to use a different {{javac}} than the one it
finds in {{JAVA_HOME}}. Perhaps we should support this for the native build as
well. Let's open a separate JIRA for that. It would be a new feature that has
never been supported in the past, and it's not a blocker for this change.
> cmake: always use JAVA_HOME to find libjvm.so, jni.h, jni_md.h
> --------------------------------------------------------------
>
> Key: HADOOP-8737
> URL: https://issues.apache.org/jira/browse/HADOOP-8737
> Project: Hadoop Common
> Issue Type: Bug
> Components: native
> Affects Versions: 2.2.0-alpha
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Priority: Minor
> Attachments: HADOOP-8737.001.patch
>
>
> We should always use the {{libjvm.so}}, {{jni.h}}, and {{jni_md.h}} under
> {{JAVA_HOME}}, rather than trying to look for them in system paths. Since we
> compile with Maven, we know that we'll have a valid {{JAVA_HOME}} at all
> times. There is no point digging in system paths, and it can lead to host
> contamination if the user has multiple JVMs installed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
