- From: Chad Woolley <
- To: Chef Dev <
- Subject: [[chef-dev]] JAVA_HOME, sun vs. openjdk inconsistencies
- Date: Tue, 1 Jun 2010 00:24:16 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=PTyGlxSwjHlmT3FMda8JHFZJnS7CqnBluTKcbwKh9t2P5OktKN5QmTFaGFnnkyANTi D3tWjPe9BpKVHwKyFUv5yriEc8AT5iU3//ry4U2+3Xsk94r2emRo23Bjsojiox4Xw59+ 7ZlMVGqp5HfTEr6C9D/CT9tUK0cdzJTT2O7gQ=
The "java" cookbook now installs OpenJDK instead of Sun's JDK.
However, other cookbooks which use Java (JIRA, Tomcat) currently use
an incorrect or inconsistent Java home - some hardcoded to the Sun
path (e.g. /usr/lib/jvm/java-6-sun in the case of JIRA), or
/usr/lib/jvm/java in the case of Tomcat.
Also, the tomcat package has the dependency on the java recipe commented.
The result is that these cookbooks don't work "out of the box".
What's the right way to resolve this?
In my opinion, the best thing would be to keep a symlink at
/usr/lib/jvm/java which points to the current java home. I'm not sure
if this should be a change in chef or the openjdk packages...
- [[chef-dev]] JAVA_HOME, sun vs. openjdk inconsistencies, Chad Woolley, 06/01/2010
Archive powered by MHonArc 2.6.16.