Summary: | java-config does not work inside a cron job | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Adrian Almenar <aalmenar> |
Component: | Current packages | Assignee: | Jason A. Mobarak (RETIRED) <aether> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bugzilla.gentoo.dominik |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 31468 |
Description
Adrian Almenar
2003-12-15 18:52:22 UTC
I think the problem is that java-config is getting the "JAVA_HOME" environment variable from the the actual environment still -- so this should be fairly easy to correct. Just for the record since I guess it has the same cause: when using java-config --jdk-home from within an init script I also only get the error message jc_options: No JDK_HOME set! Whenever JAVA_HOME is not set this will happen, it'll be changed so that JAVA_HOME is not used in the next release. Sorry, JDK_HOME rather than JAVA_HOME. This has been fixed for JAVA_HOME, I need to generalize it and apply to all functions that look for environment vars in order to determine JVM settings. Fix in 1.1.8 and 1.2.0 Version 1.1.8 is stable. |