Project

General

Profile

Actions
Copy link

Bug #2842

closed

Jetty can't be started with a JAVA_HOME which is /usr/java

Added by Nicolas PERRON about 12 years ago. Updated over 9 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
Packaging
Target version:
2.4.0~beta5
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

We need a more flexible test to set the JAVA and JAVA_HOME envars.

With java installed in /usr/java, jetty can't be started and display theses messages:

/etc/init.d/jetty restart
# /etc/init.d/jetty restart
Stopping Jetty: OK
Setting umask to 0027
Starting Jetty: /etc/init.d/jetty: line 491: /usr/bin/java: No such file or directory

Actions
Copy link
 #1

Updated by Jonathan CLARKE about 12 years ago

  • Status changed from New to 2
  • Assignee changed from Nicolas PERRON to Jonathan CLARKE
  • Target version changed from 2.4.0~beta4 to 2.4.0~beta5
Actions
Copy link
 #2

Updated by Jonathan CLARKE about 12 years ago

  • Status changed from 2 to Pending technical review
  • % Done changed from 0 to 100

Applied in changeset commit:57794790aa980a251d7df27e55bf26fe7b686011.

Actions
Copy link
 #3

Updated by Nicolas PERRON about 12 years ago

It looks valid to me.

Actions
Copy link
 #4

Updated by Jonathan CLARKE about 12 years ago

  • Status changed from Pending technical review to Released
Actions
Copy link
 #5

Updated by Nicolas PERRON almost 12 years ago

  • Project changed from Rudder to 34
  • Category deleted (11)
Actions
Copy link
 #6

Updated by Benoît PECCATTE over 9 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions
Copy link

Also available in: Atom PDF