'错误：JAVA_HOME未正确定义。'在MVN命令

，当我在Ubuntu中运行命令'错误：JAVA_HOME未正确定义。'在MVN命令

mvn version

我碰到下面的错误。

Error: JAVA_HOME is not defined correctly. We cannot execute /usr/lib/jvm/java-7-openjdk-amd64/bin/java

我的Java版本是

java version "1.8.0_91" Java(TM) SE Runtime Environment (build 1.8.0_91-b14) Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)

我跑

sudo nano /etc/environment

命令和一套Java家庭和Maven作为

JAVA_HOME="/usr/lib/jvm/java-8-oracle/jre" M2_HOME=/usr/local/apache-maven/apache-maven-3.2.5 MAVEN_HOME=/usr/local/apache-maven/apache-maven-3.2.5 M2=/usr/local/apache-maven/apache-maven-3.2.5/bin

我的PATH变量 -

/usr/share/maven3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/jvm/java-8-oracle/jre:/home/hduser/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/local/hadoop/bin:/usr/local/hadoop/sbin:/usr/local/hadoop/bin:/usr/lib/sqoop/bin:/home/hduser/bin:/usr/lib/jvm/java-8-oracle/jre/bin

和运行命令

sudo nano ~/.bashrc

，并设置这些在年底

JAVA_HOME=/usr/lib/jvm/java-8-oracle/jre PATH=$PATH:$HOME/bin:$JAVA_HOME/bin export JAVA_HOME export JRE_HOME export PATH export M2_HOME=/usr/share/maven3 export M2=$M2_HOME/bin export PATH=$M2:$PATH

我有安装java 8和删除Java 7，然后运行mvn命令，我得到这个错误。我很想知道为什么它会显示java 7而不是java 8，并且还请提供一些解决方案。在此先感谢

编辑

我的.bashrc是 -

# ~/.bashrc: executed by bash(1) for non-login shells. 
    # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) 
    # for examples 

    # If not running interactively, don't do anything 
    case $- in 
     *i*) ;; 
      *) return;; 
    esac 

    # don't put duplicate lines or lines starting with space in the history. 
    # See bash(1) for more options 
    HISTCONTROL=ignoreboth 

    # append to the history file, don't overwrite it 
    shopt -s histappend 

    # for setting history length see HISTSIZE and HISTFILESIZE in bash(1) 
    HISTSIZE=1000 

    # ~/.bashrc: executed by bash(1) for non-login shells. 
    # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) 
    # for examples 

    # If not running interactively, don't do anything 
    case $- in 
     *i*) ;; 
      *) return;; 
    esac 

    # don't put duplicate lines or lines starting with space in the history. 
    # See bash(1) for more options 
    HISTCONTROL=ignoreboth 

    # append to the history file, don't overwrite it 
    shopt -s histappend 

    # for setting history length see HISTSIZE and HISTFILESIZE in bash(1) 
    HISTSIZE=1000 
    HISTFILESIZE=2000 

    # check the window size after each command and, if necessary, 
    # update the values of LINES and COLUMNS. 
shopt -s checkwinsize 

# If set, the pattern "**" used in a pathname expansion context will 
# match all files and zero or more directories and subdirectories. 
#shopt -s globstar 

# make less more friendly for non-text input files, see lesspipe(1) 
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)" 

# set variable identifying the chroot you work in (used in the prompt below) 
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then 
    debian_chroot=$(cat /etc/debian_chroot) 
fi 

# set a fancy prompt (non-color, unless we know we "want" color) 
case "$TERM" in 
    xterm-color) color_prompt=yes;; 
esac 

# uncomment for a colored prompt, if the terminal has the capability; turned 
# off by default to not distract the user: the focus in a terminal window 
# should be on the output of commands, not on the prompt 
#force_color_prompt=yes 

if [ -n "$force_color_prompt" ]; then 
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then 
     # We have color support; assume it's compliant with Ecma-48 
     # (ISO/IEC-6429). (Lack of such support is extremely rare, and such 
     # a case would tend to support setf rather than setaf.) 
     color_prompt=yes 
    else 
     color_prompt= 
    fi 
fi 

if [ "$color_prompt" = yes ]; then 
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\[email protected]\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ ' 
else 
    PS1='${debian_chroot:+($debian_chroot)}\[email protected]\h:\w\$ ' 
fi 
unset color_prompt force_color_prompt 

# If this is an xterm set the title to [email protected]:dir 
case "$TERM" in 
xterm*|rxvt*) 
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\[email protected]\h: \w\a\]$PS1" 
    ;; 
*) 
    ;; 
esac 

# enable color support of ls and also add handy aliases 
if [ -x /usr/bin/dircolors ]; then 
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)" 
    alias ls='ls --color=auto' 
    #alias dir='dir --color=auto' 
    #alias vdir='vdir --color=auto' 

    alias grep='grep --color=auto' 
    alias fgrep='fgrep --color=auto' 
    alias egrep='egrep --color=auto' 
fi 

# some more ls aliases 
alias ll='ls -alF' 
alias la='ls -A' 

alias l='ls -CF' 

# Add an "alert" alias for long running commands. Use like so: 
# sleep 10; alert 
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*al$ 

# Alias definitions. 
# You may want to put all your additions into a separate file like 
# ~/.bash_aliases, instead of adding them here directly. 
# See /usr/share/doc/bash-doc/examples in the bash-doc package. 

if [ -f ~/.bash_aliases ]; then 
    . ~/.bash_aliases 
fi 

# enable programmable completion features (you don't need to enable 
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile 
# sources /etc/bash.bashrc). 
if ! shopt -oq posix; then 
    if [ -f /usr/share/bash-completion/bash_completion ]; then 
    . /usr/share/bash-completion/bash_completion 
    elif [ -f /etc/bash_completion ]; then 

. /etc/bash_completion 
    fi 
fi 
#======================================= 
# Added by TKS to conexport PATH=$JAVA_HOME/bin:$PATH 
figure HDFS 
#======================================= 
#HADOOP VARIABLES START 
export HADOOP_INSTALL=/usr/local/hadoop 
export PATH=$PATH:$HADOOP_INSTALL/bin 
export PATH=$PATH:$HADOOP_INSTALL/sbin 
export HADOOP_MAPRED_HOME=$HADOOP_INSTALL 
export HADOOP_COMMON_HOME=$HADOOP_INSTALL 
export HADOOP_HDFS_HOME=$HADOOP_INSTALL 
export YARN_HOME=$HADOOP_INSTALL 
export HADOOP_COMMON_LIB_NATIVE_DIR=$HADOOP_INSTALL/lib/native 
export HADOOP_OPTS="-Djava.library.path=$HADOOP_INSTALL/lib" 
export HADOOP_HOME=/usr/local/hadoop 
#export SQOOP_HOME=/usr/local/sqoop 
export PATH=$PATH:$HADOOP_HOME/bin 
#export PATH=$PATH:$SQOOP_HOME/bin 
export SQOOP_HOME=/usr/lib/sqoop 
#HADOOP VARIABLES END 
JAVA_HOME=/usr/lib/jvm/java-8-oracle 
PATH=$PATH:$JAVA_HOME/bin 
export JAVA_HOME 
export PATH 
export M2_HOME=/usr/local/apache-maven/apache-maven-3.2.5 
export M2=$M2_HOME/bin 
export PATH=$M2:$PATH

来源

2016-06-14 Parita Porwal

'echo $ JAVA_HOME'显示什么输出？它指向正确的地方吗？如果没有，还有其他的设置你的'JAVA_HOME'。 – Jesper

您是否在java 8升级后重新启动了该框？ –

'echo $ JAVA_HOME'输出是'/ usr/lib/jvm/java-8-oracle/jre'，是的它显示了我的java的正确位置 –

我觉得你JAVA_HOME应该是JDK，而不是因为Maven的JRE编译Java代码并没有Java编译器（ javac）在JRE中。

来源

2016-06-14 14:01:38

与路径上的jdk仍然我得到相同的错误 –

你可以尝试以下命令'source〜/ .bashrc'并再次尝试'mvn -version'？ –

'source〜/ .bashrc'给我'figure：command not found' –

以下应该足够：

JAVA_HOME =/usr/lib中/ JVM/JAVA -8-预言

M2_HOME =的/ usr /本地/ Apache-行家/ Apache的行家-3.2.5

PATH = $ PATH：$ JAVA_HOME/bin中

PATH = $ PATH：$ M2_HOME/bin

删除您声明的其他变量M2或MAVEN_HOME。

来源

2016-06-14 14:29:44

不，这不能解决我的问题 –

'错误：JAVA_HOME未正确定义。'在MVN命令

回答

相关问题