Goal: Increased Modularity?

[Richi Plana]

On Wed, 2007-09-05 at 12:33 -0500, Les Mikesell wrote:
> So, where do I find the answer to the question above regarding the 
> correct JAVA_HOME and PATH to use a JVM that is not the system default?
> How is the split exports/private directory supposed to relate to that?

On my system where I have java-1.5.0-sun-1.5.0.12-1jpp.x86_64 and
java-1.5.0-sun-devel-1.5.0.12-1jpp.x86_64 installed, I use

JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun-1.5.0.12
# and
PATH=$JAVA_HOME/bin:$PATH

which works regardless of what alternatives has set up. If you
use /usr/bin/java, though, I assume it overwrites JAVA_HOME. But if you
just the executable loader find java, then it should use the
above-mentioned properly. At least I haven't had any issues.

> And what's the current situation with this now that Fedora and RHEL5 
> include some stuff that looks jpackage'd but isn't?   How do you 
> control, for example, which tomcat version you install?

As far as I can tell, the init scripts that come with tomcat5 for Fedora
Core 6 (the only ones I've tested so far) uses $(JAVA_HOME)/bin/java ...
that's the JAVA_HOME set for the tomcat5 user. It's CATALINA_HOME is set
to /usr/share/tomcat5/ and it configured (again for the Fedora package)
via /etc/tomcat5/tomcat5.conf
--

Richi Plana