accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charles Butterfield (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4193) Server/Native build fails with "JAVA_HOME does not point to a JDK" - possible regression from 1.7.1
Date Sun, 17 Apr 2016 22:31:25 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244949#comment-15244949
] 

Charles Butterfield commented on ACCUMULO-4193:
-----------------------------------------------

Interesting - when I use "mvn verifiy" on branch 1.7 without a JDK, the build fails at the
test-native-libs step.  Setting the JAVA_HOME to point to a JDK gets past that point.  Sounds
like I was just building improperly and "got lucky" with using a JRE.  I'll just change my
build environment to point to a JDK.  Sorry for the confusion, sounds like this ticket should
be closed.

> Server/Native build fails with "JAVA_HOME does not point to a JDK" - possible regression
from 1.7.1
> ---------------------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-4193
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4193
>             Project: Accumulo
>          Issue Type: Bug
>          Components: native
>         Environment: CentOS 6.7, Java-8
> git commit 8ac30b8d16316e3e03054cfb3786e6b857b528c0
>            Reporter: Charles Butterfield
>            Assignee: Christopher Tubbs
>            Priority: Minor
>
> Building from the git repo fails, while building from the 1.7.1 src download works fine
(on the same system).  I can easily work around the problem by redefining JAVA_HOME to point
to a JDK.  The fact that everything works find with 1.7.1 makes me wonder if the JDK is really
required.
> [INFO] --- exec-maven-plugin:1.4.0:exec (test-native-libs) @ accumulo-native ---
> Makefile:45: *** "JAVA_HOME does not point to a JDK. Exiting...".  Stop.
> Hmmm, I'm thinking I'll reboot the build VM and retry each build just in case there is
some "operator error" involved.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message