Bug #2635
closed
Starting jetty complain about directory missing on SuSE
Description
Using /etc/init.d/jetty result of:
find: `/usr/lib/jvm': No such a file or directory
It comes from the first line of /etc/default/jetty:
JAVA_HOME=$(find /usr/lib/jvm -maxdepth 1 -type d -name java-7-openjdk-i386 -or -name java-7-openjdk-amd64 -or -name java-6-sun | sort -r | head -n1)
We should hid this message.
Updated by Nicolas PERRON over 12 years ago
- Target version changed from 2.4.0~beta2 to 2.4.0~beta3
2.4.0~beta2 has been released. This ticket must be moved to 2.4.0~beta3.
Updated by Jonathan CLARKE over 12 years ago
- Status changed from New to Pending technical review
- % Done changed from 0 to 100
Applied in changeset commit:799a4c727e2b8961954f7871951c29974689925c.
Updated by Jonathan CLARKE over 12 years ago
- Assignee changed from Nicolas PERRON to Jonathan CLARKE
Updated by Nicolas PERRON over 12 years ago
It seems OK to me but we could check the java repository for SLES too (/usr/java) even if the java folder's names are different (jre1.* or jdk1.*).
Updated by Jonathan CLARKE about 12 years ago
- Status changed from Pending technical review to Released
Nicolas PERRON wrote:
It seems OK to me but we could check the java repository for SLES too (/usr/java) even if the java folder's names are different (jre1.* or jdk1.*).
I think this is less necessary, as you often have several JREs installed on Debian/Ubuntu due to their broken dependencies in the java bits... On a pretty standard SLES machine, you would only have one JRE, or have several but manage the machine wide JAVA_HOME env variable. Maybe we can do this in another ticket?
Updated by Nicolas PERRON almost 12 years ago
- Project changed from Rudder to 34
- Category deleted (
11)
Updated by Benoît PECCATTE over 9 years ago
- Project changed from 34 to Rudder
- Category set to Packaging