JAVA_HOME Variable error while installing groundwork

Forum Index » Forums » Applications
Author Message
Joined: May 26, 2008
Posts: 19
Other Topics
Posted Jul 30, 2008 at 10:10:00 AM
Subject: JAVA_HOME Variable error while installing groundwork
hi forum. i have recntly been trying to install GroundWork Monitor Open Source 5.1.0 on a Hp Intel machine with 3Ghz procesor and 1Gb ram running fedora 8. Everything seems to be ok but java seems to have a problem whenever i try to install groundwork-foundation it indicates that the JAVA_HOME variable is incorrectly set. Here is the error:: [code=xml] The JAVA_HOME environment variable is not defined correctly. This environment variable is needed to run this program. NB: JAVA_HOME should point to a JDK not a JRE. error: %pre(groundwork-foundation-pro-2.0.1-48.noarch) scriptlet failed, exit status 1 error: install: %pre scriptlet failed (2), skipping groundwork-foundation-pro-2.0.1-48 [/code] I added the following lines to the end of the /etc/profile file [code=xml] export JAVA_HOME=/usr/java/jdk1.5.0_06 export PATH=$PATH:$JAVA_HOME/bin [/code] i have followed the groundwork manual precisely including the part where you set the JAVA_HOME variable and not sure of what the error means. Ps. i had a previous newer installation of java(default one in fedora installation) which i just overwrote using rpm -i --force jdk*.rpm, Could this be the cause of the error? I think the same java home variable error also causes my terminal to display 'bash: ‘export: command not found' twice every time a new terminal screen is started.
Back to top Profile Email Website
Johannes Truschnigg

Joined Jun 15, 2008
Posts: 27

Other Topics
Posted: Jul 30, 2008 12:42:06 PM
JAVA_HOME usually has to bet set to the path from where "bin/java" (the JRE's main executable) is found. On your shell, you might get to know where your `java`-binary lives when running `type -p java`, or `which java`. If the output, for example, reads "/usr/bin/java", your JAVA_HOME is "/usr". Modifying the environment of all your users in such a way that their PATH (and their environment itself) contains JAVA_HOME almost certainly is not necessary, and editing /etc/profile is vain anyway - it will be overwritten by your distro at some point in time in the future; there has to be another way to modify your default environment in its init process. Why your version of bash is lacking the `export` built-in really is beyond me; however, if only the installer of the app in question need JAVA_HOME to be set, there's no need at all to modify your environment in a persistent manner; running JAVA_HOME=/some/path/correct/for/your/setup /path/to/installer/executable` should do the job just fine. Hth.

Free software. Free society. Better lives.

Back to top Profile Email Website
hailer
Joined May 26, 2008
Posts: 19

Other Topics
Posted: Aug 01, 2008 9:22:21 AM
Thanks Johannes Truschnigg for the reply but i managed to fix the problem. It seemed like i was the one who defiled a link incorrectly causing a whole lot of issues with groundwork installation.
Back to top Profile Email Website
Forum Index » Forums » Applications