[ 
https://issues.apache.org/jira/browse/HADOOP-8742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Colin Patrick McCabe updated HADOOP-8742:
-----------------------------------------

    Description: 
Maven supports compiling software with a different {{javac}} than the one under 
the current {{JAVA_HOME}}.  See 
http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html
 for details.

Although we have never supported this in the past, in the future we could 
support compiling the native code with a JDK other than the one referenced by 
the JDK in use by Maven.  Probably we would add a system property that could be 
passed in on the command-line.  Perhaps {{-Dnative.jdk.path=...}}.

Another thing to keep in mind is that the native build currently considers 
certain properties of the current Java environment when building.  For example, 
the native build checks {{sun.arch.data.model}} to see if it should build a 
32-bit or 64-bit native build.  We would have to make sure that this worked 
correctly with any "separate native JDK" feature we added.

  was:
Maven supports compiling software with a different {{java}} than the one under 
the current {{JAVA_HOME}}.  See 
http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html
 for details.

Although we have never supported this in the past, in the future we could 
support compiling the native code with a JDK other than the one referenced by 
the JDK in use by Maven.  Probably we would add a system property that could be 
passed in on the command-line.  Perhaps {{-Dnative.jdk.path=...}}.

Another thing to keep in mind is that the native build currently considers 
certain properties of the current Java environment when building.  For example, 
the native build checks {{sun.arch.data.model}} to see if it should build a 
32-bit or 64-bit native build.  We would have to make sure that this worked 
correctly with any "separate native JDK" feature we added.

    
> Support compiling the native build with a different javac than the one under 
> JAVA_HOME
> --------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8742
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8742
>             Project: Hadoop Common
>          Issue Type: New Feature
>          Components: native
>            Reporter: Colin Patrick McCabe
>            Priority: Trivial
>
> Maven supports compiling software with a different {{javac}} than the one 
> under the current {{JAVA_HOME}}.  See 
> http://maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.html
>  for details.
> Although we have never supported this in the past, in the future we could 
> support compiling the native code with a JDK other than the one referenced by 
> the JDK in use by Maven.  Probably we would add a system property that could 
> be passed in on the command-line.  Perhaps {{-Dnative.jdk.path=...}}.
> Another thing to keep in mind is that the native build currently considers 
> certain properties of the current Java environment when building.  For 
> example, the native build checks {{sun.arch.data.model}} to see if it should 
> build a 32-bit or 64-bit native build.  We would have to make sure that this 
> worked correctly with any "separate native JDK" feature we added.

--
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

Reply via email to