Bug 3355 – $JAVA_HOME/bin/java vs [[PATH]] java

Bug 3355 - $JAVA_HOME/bin/java vs [[PATH]] java

Summary:

$JAVA_HOME/bin/java vs [[PATH]] java

Status:	RESOLVED FIXED

Product:	GRAM
Component:	gt2 Gatekeeper/Jobmanager
Version:	4.0.0
Platform:	PC Linux

Importance:	P3 minor
Target Milestone:	4.0.2
Assigned To:	Stuart Martin

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-05-16 09:49 by Jens-S. Vöckler
Modified:	2005-08-31 11:31 (History)

Attachments
log file from automatic make (323.17 KB, text/plain) 2005-05-16 09:50, Jens-S. Vöckler	Details
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Jens-S. Vöckler 2005-05-16 09:49:12

Something appears to have changed recently with post-install? The postinstaller
now insists on a java in my PATH instead of using the one in $JAVA_HOME/bin.
Yes, my PATH was "mis-set" lacking the java (because it was a cron job), but my
JAVA_HOME was set. Why doesn't it use the one from JAVA_HOME in the absence of a
java in the PATH?

------- Comment #1 From Jens-S. Vöckler 2005-05-16 09:50:57 -------

Created an attachment (id=611) [details]
log file from automatic make

This shows that in the "make install" step it died on missing java. It did not
have any such problem during the "make" itself, though.

------- Comment #2 From Charles Bacon 2005-05-31 10:17:01 -------

It looks like the trouble is in the GRAM setup script, not in the postinstall
itself.

It's a feature of ant that it looks in JAVA_HOME/bin in addition to the path,
not of the installer itself.

------- Comment #3 From Stuart Martin 2005-08-31 11:31:15 -------

I made the change to that if java is not found in the PATH, but JAVA_HOME is
set, then append 
JAVA_HOME/bin to the PATH.  This should solve the problem.