[
https://issues.apache.org/jira/browse/GERONIMO-5142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837080#action_12837080
]
Kevan Miller commented on GERONIMO-5142:
----------------------------------------
Right. Almost any *nix system is going to have a symbolic link in PATH to the
actual java executable. So the shell script would need to follow symbolic
links until it found the actual executable. This is certainly possible to do.
I also seem to recall the mvn script having some platform specific code for
finding JAVA_HOME.
I'd prefer we were a 1) consistent between Windoze .bat and reasonable OS .sh
environments (e.g. require or not require JAVA/JRE_HOME) and 2) allowed
JAVA/JRE_HOME to default, if not explicitly set.
FYI, just checked Tomcat. Looks like their setclasspath.sh would be a
reasonable guide.
> runtime errors if JAVA_HOME or JRE_HOME is not specified
> --------------------------------------------------------
>
> Key: GERONIMO-5142
> URL: https://issues.apache.org/jira/browse/GERONIMO-5142
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.1.4, 2.2
> Reporter: Kevan Miller
> Fix For: 2.1.5, 2.2.1
>
>
> setjavaenv.sh used to require JAVA_HOME or JRE_HOME to be specified. Looks
> like it was updated to look for a java runtime in the PATH, and use that, if
> the environment variables weren't specified.
> On Mac OS, at least, this doesn't work. JAVA_HOME/JRE_HOME are used to set
> other variables. Namely EXT_DIRS and ENDORSED_DIRS. They aren't set properly,
> if JAVA_HOME/JRE_HOME aren't set. This causes runtime errors:
> Module 19/70 org.apache.geronimo.configs/openejb/2.1.4/car
>
> 2010-02-11 09:48:23,404 ERROR [SimpleEncryption] Unable to decrypt
> java.security.NoSuchAlgorithmException: Cannot find any provider supporting
> AES
> at javax.crypto.Cipher.getInstance(DashoA13*..)
> at
> org.apache.geronimo.crypto.AbstractEncryption.decrypt(AbstractEncryption.java:74)
> at
> org.apache.geronimo.crypto.EncryptionManager.decrypt(EncryptionManager.java:109)
> ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
